[ 
https://issues.apache.org/jira/browse/FLINK-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175297#comment-17175297
 ] 

wangxiyuan commented on FLINK-13598:
------------------------------------

Yes, I tried and built Frocksdb 5.17.2 successful on ARM64[1]. And it's used 
for daily arm64 test[2]. It looks that all work well in Flink[3]. 

 

Although Rocksdb supports arm64 in its new release, Frocksdb is a fork from 
Rocksdb and has its own private change and the higher Rocksdb version has some 
perforamance issue. So that we can't upgrade Frocksdb to a newer Rocksdb 
version.

 

For Frocksdb 5.17.2 itself, the problem is that the test (run `make 
check_some`) can't be fully passed on arm64. Base on the test I ran a few 
months ago, there are 1-3 test failures. (I can't remember the exact number).

 

[1]: 
[https://github.com/wangxiyuan/Toy/blob/master/package/rocksdbjni-5.17.2-linux64.jar]

[2]: 
[https://github.com/theopenlab/openlab-zuul-jobs/blob/master/playbooks/flink-end-to-end-test/common.yaml#L30]

[3]: 
[http://status.openlabtesting.org/builds?job_name=flink-build-and-test-arm64-core-and-tests]

> 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)

Reply via email to