[
https://issues.apache.org/jira/browse/FLINK-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180907#comment-17180907
]
wangxiyuan commented on FLINK-13598:
------------------------------------
[~yunta] , hi, if you bump rocksdb to the version higher than 5.18.4 or 6.4.6,
you don't need to do anything for code change, because Rocksdb has supported
arm64 from that version already. You only need to build it on arm64 to get the
librocksdbjni-linux-aarch64.so file then package it to frocksdbjni.jar.
[https://mvnrepository.com/artifact/org.rocksdb/rocksdbjni/6.4.6]
I know there are still some blockers. Like what you and [~rmetzger] pointed:
performance regression, arm64 infrastructure, committer maintainability and so
on. It need time to solve. Looking forward for community's working!
Here I can just bring up my thought about arm64 infrastructure problem: for
Frocksdb ARM64 CI, how about using Travis? It's what Rocksdb uses. And OpenLab
can provide some VMs for package release as well.
> 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
> Attachments: image-2020-08-20-09-22-24-021.png
>
>
> 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)
