Zakelly opened a new pull request, #23509:
URL: https://github.com/apache/flink/pull/23509

   ## What is the purpose of the change
   
   By default, Flink creates subdirectories named by UUID (job id) under 
checkpoint directory for each job. It's a good means to avoid collision. 
However, it also bring in some effort to remember/find the right directory when 
recovering from previous checkpoint, as well as cleaning the old 
subdirectories. According to previous discussion ([Yun 
Tang's](https://issues.apache.org/jira/browse/FLINK-11789?focusedCommentId=16782314&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16782314)
 and [Stephan 
Ewen's](https://issues.apache.org/jira/browse/FLINK-9043?focusedCommentId=16409254&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16409254)
 ), I think it would be useful to add an option to disable creating the UUID 
subdirectories under the checkpoint directory. For compatibility 
considerations, we create the subdirectories by default.
   
   
   ## Brief change log
   
    - Provide a new configuration named 'state.checkpoints.create-subdir' to 
control the behavior of creating job-id subdirectories under the checkpoint 
directory or not. This is an advanced option, which is well documented and 
warned.
   
   
   ## Verifying this change
   
   This change is already covered by newly added tests, a parameterized 
AbstractFileCheckpointStorageAccessTestBase#testCreateCheckpointSubDirs .
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), **Checkpointing**, Kubernetes/Yarn, ZooKeeper: (**yes** / no / 
don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (**yes** / no)
     - If yes, how is the feature documented? (not applicable / **docs** / 
JavaDocs / not documented)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to