You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stefan Richter (JIRA)" <ji...@apache.org> on 2018/05/02 08:13:00 UTC
[jira] [Closed] (FLINK-9270) Upgrade RocksDB to 5.11.3, and resolve
concurrent test invocation problem of @RetryOnFailure
[ https://issues.apache.org/jira/browse/FLINK-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Richter closed FLINK-9270.
---------------------------------
Resolution: Won't Fix
Won't fix until we figure out a way around the performance regression of the merge operator in newer versions of RocksDB.
> Upgrade RocksDB to 5.11.3, and resolve concurrent test invocation problem of @RetryOnFailure
> --------------------------------------------------------------------------------------------
>
> Key: FLINK-9270
> URL: https://issues.apache.org/jira/browse/FLINK-9270
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Affects Versions: 1.5.0
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Major
> Fix For: 1.6.0
>
>
> Upgrade RocksDB to 5.11.3 to take latest bug fixes
> Besides, I found that unit tests annotated with {{@RetryOnFailure}} will be run concurrently if there's only {{try}} clause without a {{catch}} following. For example, sometimes, {{RocksDBPerformanceTest.testRocksDbMergePerformance()}} will actually be running in 3 concurrent invocations, and multiple concurrent write to RocksDB result in errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)