[
https://issues.apache.org/jira/browse/FLINK-8922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401925#comment-16401925
]
Sihua Zhou commented on FLINK-8922:
-----------------------------------
Ah, happy to tell you guys that finally I find the way to make it works
correctly. Indeed I think it's [~aljoscha] that found the way to overcome this,
as the comments he left, I change to code to re-introduce a {{private final
WriteOptions;}} for every state (not sharing only one {{WriteOptions}} accross
all {{State}}), and also a dedicated {{WriteOptions}} for restoring. After the
above works, the code runs pretty fine on Travis. ;) Now, I am a bit worried
that the current code maybe problematic and
[FLINK-8845|https://issues.apache.org/jira/browse/FLINK-8845] is just a trigger
that fire this issue, [~StephanEwen] [~srichter] WDYT of this, should we make a
PR to address it for 1.5?
> 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)
