[
https://issues.apache.org/jira/browse/FLINK-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010885#comment-17010885
]
Yun Tang commented on FLINK-15318:
----------------------------------
[~redmark-ibm] can you retry the official RocksDB to see whether could meet
this problem:
* Edit {{flink-state-backends/flink-statebackend-rocksdb/pom.xml}} to use
rocksDB instead of FrocksDB
{code:java}
<dependency>
<groupId>org.rocksdb</groupId>
<artifactId>frocksdbjni</artifactId>
<version>5.17.2</version>
</dependency>
{code}
* Edit
{{flink-state-backends/flink-statebackend-rocksdb/src/main/java/org/apache/flink/contrib/streaming/state/ttl/RocksDbTtlCompactFiltersManager.java}}
to drop all usage of {{org.rocksdb.FlinkCompactionFilter}} and
{{org.rocksdb.FlinkCompactionFilter.FlinkCompactionFilterFactory}}. Remove them
would not affect you to run that test.
By doing so, you could verify whether the problem still existed for official
RocksDB.
> RocksDBWriteBatchPerformanceTest.benchMark fails on ppc64le
> -----------------------------------------------------------
>
> Key: FLINK-15318
> URL: https://issues.apache.org/jira/browse/FLINK-15318
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks, Runtime / State Backends
> Environment: arch: ppc64le
> os: rhel7.6, ubuntu 18.04
> jdk: 8, 11
> mvn: 3.3.9, 3.6.2
> Reporter: Siddhesh Ghadi
> Priority: Major
> Attachments: surefire-report.txt
>
>
> RocksDBWriteBatchPerformanceTest.benchMark fails due to TestTimedOut, however
> when test-timeout is increased from 2s to 5s in
> org/apache/flink/contrib/streaming/state/benchmark/RocksDBWriteBatchPerformanceTest.java:75,
> it passes. Is this acceptable solution?
> Note: Tests are ran inside a container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
