[
https://issues.apache.org/jira/browse/FLINK-8922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402328#comment-16402328
]
Stephan Ewen commented on FLINK-8922:
-------------------------------------
[~sihuazhou]'s findings could be the right fix.
Could it be that RocksDB itself releases in some case the native object for the
WriteOptions (or something that this internally points to)?
In that case, having a dedicated options object per state and for restore may
be the best way to handle this.
Technically, I would still consider this a bug in RocksDB and this solution a
workaround for the bug. But that what we need to do sometimes...
> 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)
