[
https://issues.apache.org/jira/browse/FLINK-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014379#comment-17014379
]
Ronald O. Edmark commented on FLINK-15318:
------------------------------------------
[~yunta] thanks again for helping.
This is a Red Hat 7.6 KVM hosted virtual machine, ppc64le with 16 GB of memory,
8 GB swap, 4 cpus.
Currently our only solution is to change the performance write time-out from 2
seconds to 3 seconds in
```
./flink-state-backends/flink-statebackend-rocksdb/src/test/java/org/apache/flink/contrib/streaming/state/benchmark/RocksDBWriteBatchPerformanceTest.java
[*@Test*|https://jazz06.rchland.ibm.com:12443/jazz/users/Test]*(timeout = 2000)
change to [@Test|https://jazz06.rchland.ibm.com:12443/jazz/users/Test](timeout
= 3000)*
*```*
> 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)
