[
https://issues.apache.org/jira/browse/FLINK-15692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019872#comment-17019872
]
Yun Tang commented on FLINK-15692:
----------------------------------
[~ptmagic] since you did not take participated in any discussion or code
contribution of sub-tasks in FLINK-7289. I don't know how much you know well
for the background knowledge. From what we can see so far, the behavior of
write buffer manager and lru cache is not exactly like rocksDB doc said, we
need to spend some energy to dig into RocksDB's internal implementation.
It's not saying that flink community is not welcome for new-come developers,
it's more like concern for an important feature which prefer some guys could
focus on that from end to end. We're very happy that more and more guys could
contribute Flink and make it better, but my two cents would suggest new guys
could start from taken participated in discussion first or pick a new story.
Hope this does not make you feel unhappy.
> Enable limiting RocksDB memory consumption by default
> -----------------------------------------------------
>
> Key: FLINK-15692
> URL: https://issues.apache.org/jira/browse/FLINK-15692
> Project: Flink
> Issue Type: Task
> Components: Runtime / State Backends
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Priority: Blocker
> Fix For: 1.10.0
>
>
> Enable limiting RocksDB memory consumption by default. This means to change
> the default value of {{state.backend.rocksdb.memory.managed}} to {{true}}.
> This will change Flink's default behaviour for many users but I believe the
> benefits of a much more predictable memory behaviour of Flink will outweigh
> the downside of having fewer memory available.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
