[
https://issues.apache.org/jira/browse/FLINK-8922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395205#comment-16395205
]
Stefan Richter commented on FLINK-8922:
---------------------------------------
Yes, I tried out to create a dedicated \{{WriteOptions}} object only for the
restore loop and it still failed. What worries me most is that there is no
obvious difference between what restore does and how a state accesses RocksDB.
My suggestion is that after the release, we should figure out a) the actual
test that fails and b) the reason why it fails. If the reason is a bug in
RocksDB, then there is either the option to keep WAL active, fix it, or get it
fixed by the maintainers.
> Revert FLINK-8859 because it causes segfaults in testing
> --------------------------------------------------------
>
> Key: FLINK-8922
> URL: https://issues.apache.org/jira/browse/FLINK-8922
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.5.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Fix For: 1.5.0
>
>
> We need to revert FLINK-8859 because it causes problems with RocksDB that
> make our automated tests fail on Travis. The change looks actually good and
> it is currently unclear why this can introduce such a problem. This might
> also be a Rocks in RocksDB. Nevertheless, for the sake of a proper release
> testing, we should revert the change for now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
