You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2018/07/31 09:23:33 UTC

[GitHub] azagrebin opened a new pull request #6460: [FLINK-9938] Clean up full snapshot from expired state with TTL

azagrebin opened a new pull request #6460: [FLINK-9938] Clean up full snapshot from expired state with TTL
URL: https://github.com/apache/flink/pull/6460
 
 
   ## What is the purpose of the change
   
   This PR introduces optional cleaning up of state snapshot from expired state during full scan snapshotting strategies (sync/async heap backend and rocksdb non-incremental).
   
   At the moment, this reduces size only of the stored snapshot. The local running state is not cleaned up actively but will decrease after restore. This might change if we introduce e.g. a thread safe queue of potentially expired keys and pull it incrementally for cleanup when we touch local state during normal operation.
   
   ## Brief change log
   
     - Add *CleanupStrategies* to *StateTtlConfig*
     - 
     - drop *ttl* prefixes and reduce verbosity in *StateTtlConfig*
   
   ## Verifying this change
   
   TTL unit tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (not documented yet)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services