You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aaron Levin (Jira)" <ji...@apache.org> on 2019/09/18 16:53:00 UTC
[jira] [Closed] (FLINK-14111) Flink should be robust to a
non-leader Zookeeper host going down
[ https://issues.apache.org/jira/browse/FLINK-14111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Levin closed FLINK-14111.
-------------------------------
Resolution: Duplicate
Closing in favour of: https://issues.apache.org/jira/browse/FLINK-10052
> Flink should be robust to a non-leader Zookeeper host going down
> ----------------------------------------------------------------
>
> Key: FLINK-14111
> URL: https://issues.apache.org/jira/browse/FLINK-14111
> Project: Flink
> Issue Type: Wish
> Components: Runtime / Coordination
> Affects Versions: 1.7.2, 1.8.0, 1.8.1, 1.9.0
> Environment: Linux
> JVM 8
> Flink {{1.7.2}}, {{1.8.1}}, {{1.9.0}}
> {{Zookeeper version 3.4.5}}
> Reporter: Aaron Levin
> Priority: Major
>
> I noticed that if a non-leader Zookeeper node goes down and there is still quorom in the zookeeper cluster , my flink application will restart anyway. I believe it should be possible for Flink applications not to require a restart in this scenario.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)