[
https://issues.apache.org/jira/browse/FLINK-25296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470019#comment-17470019
]
Anton Kalashnikov commented on FLINK-25296:
-------------------------------------------
Hi [~libra_816]. I have checked your scenario but unfortunately, I could not
reproduce it. All my attempts worked perfectly fine.
Some questions for clarification:
* Do you able to reproduce this problem every time or did you see it only once?
* How many checkpoints maximum do you see in the folder when you launch a job
without `retained` argument?
* Do you run the default configuration or do you have your own
`flink-conf.yaml`(or modified TopSpeedWindowing directly)?
In general, I don't see any special code for handling the default of
`state.checkpoints.num-retained` it should work in the same way as for any
other configurations. So please, try one more time clean experiment with
minimum changes of the default configuration.
> [state.checkpoints.num-retained ]The default value does not take effect
> -----------------------------------------------------------------------
>
> Key: FLINK-25296
> URL: https://issues.apache.org/jira/browse/FLINK-25296
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing, Runtime / Coordination
> Affects Versions: 1.13.3
> Reporter: chenqizhu
> Priority: Major
>
> The configration is valid only when I add -Dstate.checkpoints.num-retained=n
> via command-Line Interface
> If I do not specify this configuration, the default value does not take
> effect , is it a bug ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
