[
https://issues.apache.org/jira/browse/FLINK-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180733#comment-17180733
]
Yun Tang commented on FLINK-13598:
----------------------------------
[~wangxiyuan], first of all, we should bump the version of based RocksDB as we
need the future of [direct buffer via
JNI|https://github.com/facebook/rocksdb/pull/2283] and [fix to allow strict
block cache|https://github.com/facebook/rocksdb/issues/6247]. However, there
might still existed some performance regression via our internal state
benchmark and we need to confirm that before bumping our version.
BTW, as we plan to simplify FRocksDB to a plugin based on RocksDB as
dependency, I'm not sure how much work do you still need to support ARM
platform especially if we upgrade to RocksDB-6.x
> frocksdb doesn't have arm release
> ----------------------------------
>
> Key: FLINK-13598
> URL: https://issues.apache.org/jira/browse/FLINK-13598
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / State Backends
> Affects Versions: 1.9.0, 2.0.0
> Reporter: wangxiyuan
> Priority: Major
>
> Flink now uses frocksdb which forks from rocksdb for module
> *flink-statebackend-rocksdb*. It doesn't contain arm release.
> Now rocksdb supports ARM from
> [v6.2.2|https://search.maven.org/artifact/org.rocksdb/rocksdbjni/6.2.2/jar]
> Can frocksdb release an ARM package as well?
> Or AFAK, Since there were some bugs for rocksdb in the past, so that Flink
> didn't use it directly. Have the bug been solved in rocksdb already? Can
> Flink re-use rocksdb again now?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
