flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4340) Remove RocksDB Semi-Async Checkpoint Mode
Date Tue, 09 Aug 2016 14:22:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413596#comment-15413596
] 

ASF GitHub Bot commented on FLINK-4340:
---------------------------------------

Github user wenlong88 commented on the issue:

    https://github.com/apache/flink/pull/2345
  
    @aljoscha we use rocksdb checkpoint machanism to do the semi-async checkpoint, which use
hard link to make checkpoint, cost quite a little IO and time in synchronized phrase. This
works well even when the state is large. and using the checkpoint dir to restore is also very
fast, since no extra IO need, if the task manager didn't changed.


> Remove RocksDB Semi-Async Checkpoint Mode
> -----------------------------------------
>
>                 Key: FLINK-4340
>                 URL: https://issues.apache.org/jira/browse/FLINK-4340
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.1.0
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>
> This seems to be causing to many problems and is also incompatible with the upcoming
key-group/sharding changes that will allow rescaling of keyed state.
> Once this is done we can also close FLINK-4228.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message