You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/09 13:19:20 UTC
[jira] [Commented] (FLINK-4340) Remove RocksDB Semi-Async
Checkpoint Mode
[ https://issues.apache.org/jira/browse/FLINK-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413493#comment-15413493 ]
ASF GitHub Bot commented on FLINK-4340:
---------------------------------------
GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/2345
[FLINK-4340] Remove RocksDB Semi-Async Checkpoint Mode
This was causing to many problems and is also incompatible with the
upcoming key-group/sharding changes.
R: @StephanEwen for review, should be fairly easy, though
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink rocksdb/remove-semi-async
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2345.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2345
----
commit 521f93c01bc1b99805d41eee5ab9f5279f52c4bd
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2016-08-09T13:16:59Z
[FLINK-4340] Remove RocksDB Semi-Async Checkpoint Mode
This was causing to many problems and is also incompatible with the
upcoming key-group/sharding changes.
----
> 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)