[
https://issues.apache.org/jira/browse/FLINK-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415394#comment-15415394
]
ASF GitHub Bot commented on FLINK-4340:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2345
We are very much trying to avoid different db instances per operator. Each
db instance will add quite a big new memory footprint. For higher
max-parallelism, this will be a problem.
The current philosophy in Flink was to avoid such situations, where a user
has to very carefully choose a parameter (like max parallelism) and where a
wrong setting for the parameter would lead to an unstable system.
> 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)
