You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2018/04/28 08:31:00 UTC

[jira] [Updated] (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 ]

Bowen Li updated FLINK-9270:
----------------------------
    Description: 
Upgrade RocksDB to 5.11.3

Besides, I found that unit tests annotated with {{@RetryOnFailure}} will be run concurrently. For example, sometimes, unit test with {{@RetryOnFailure(times=3)}} will actually be running in 3 concurrent invocations from the beginning, and any of their success will lead to success of the unit test. But with RocksDB unit test, that behavior can lead to test failures because multiple concurrent write.

> 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
> Besides, I found that unit tests annotated with {{@RetryOnFailure}} will be run concurrently. For example, sometimes, unit test with {{@RetryOnFailure(times=3)}} will actually be running in 3 concurrent invocations from the beginning, and any of their success will lead to success of the unit test. But with RocksDB unit test, that behavior can lead to test failures because multiple concurrent write.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)