[
https://issues.apache.org/jira/browse/FLINK-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458687#comment-16458687
]
Stephan Ewen commented on FLINK-9270:
-------------------------------------
Do we know why the merge operator regressed again? Was there a problem with the
current implementation?
> 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)
