[
https://issues.apache.org/jira/browse/FLINK-8922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401917#comment-16401917
]
Stephan Ewen commented on FLINK-8922:
-------------------------------------
[~srichter] and me had a discussion about this today.
*Can we confirm that this only happens on Travis, but not on the developer
machines (laptops)?*
If that is the case, it could be possible that this crash is in fact caused by
the specific environment on Travis CI, like a specific version of glibc, or so.
We saw in the past that RocksDB was sensitive to certain library versions
(works with certain docker base images, but not others).
If we believe that is true, we could actually deactivate WAL by default, except
for when we run on Travis (can check environment variables for that).
We need to ensure sufficient test runs on other machines, though. We (at data
Artisans) are currently working towards continuous regression runs (on some
cloud resources) which could cover that.
> 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)
