[
https://issues.apache.org/jira/browse/FLINK-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-10063.
-----------------------------------
Resolution: Fixed
Fixed via
master:
812ac8b2a13bb71cf4e5859b245cf13dfddbd222
c029d2af9de1346cf3372a55fff663cd9b61e3f1
1.6.1:
a8d2f904df2d607c934b4f3a4f17c35e12d6b48b
bdab563b7f05b96ac0d0a582fdfa3bd235ec8e17
> Jepsen: Automatically restart Mesos Processes
> ---------------------------------------------
>
> Key: FLINK-10063
> URL: https://issues.apache.org/jira/browse/FLINK-10063
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.6.0
> Reporter: Gary Yao
> Assignee: Gary Yao
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.6.1, 1.7.0
>
>
> Use a process supervisor to automatically restart Mesos processes. This is
> needed because Mesos uses a "fail-fast" approach to error handling, e.g., the
> Mesos master will exit when it discovers it has been partitioned away from
> the Zookeeper quorum. Currently the some of the tests cannot pass because the
> Mesos processes exiting.
> *Acceptance Criteria*
> * Running tests with {{--deployment-mode mesos-session}} should not fail due
> to reasons related to the Mesos setup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
