[
https://issues.apache.org/jira/browse/FLINK-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933238#comment-16933238
]
Andrey Zagrebin commented on FLINK-13598:
-----------------------------------------
I agree with [~carp84], we need to do thorough testing before we upgrade
RocksDB version (now it is 5.17.2 w/o arm support). Ideally there should be no
performance regression after the upgrade.
As [~StephanEwen] mentioned, we ideally want to firstly move back to vanilla
RocksDB to avoid rebuilding it all the time as we do it with FRocksDB. For
that, we need to finish build scripts for
[https://github.com/azagrebin/flink-rocksdb-plugins].
> 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)
