[ https://issues.apache.org/jira/browse/FLINK-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-9456. -------------------------------- Resolution: Fixed Fixed via 1.6.0: 89cfeaa882f9e68df2bd215563622b48c29a9ec9 50c0ea8c9fe17278d45aba476a95791152a1420b 1.5.1: a2f43b4cc081d360cd59ce3e7fb875e4b5fd243f 627412c4d2ea655271fe5da67a55ac936a1a060e > Let ResourceManager notify JobManager about failed/killed TaskManagers > ---------------------------------------------------------------------- > > Key: FLINK-9456 > URL: https://issues.apache.org/jira/browse/FLINK-9456 > Project: Flink > Issue Type: Improvement > Components: Distributed Coordination > Affects Versions: 1.5.0 > Reporter: Till Rohrmann > Assignee: Sihua Zhou > Priority: Major > Labels: pull-request-available > Fix For: 1.6.0, 1.5.1 > > > Often, the {{ResourceManager}} learns faster about TaskManager > failures/killings because it directly communicates with the underlying > resource management framework. Instead of only relying on the > {{JobManager}}'s heartbeat to figure out that a {{TaskManager}} has died, we > should additionally send a signal from the {{ResourceManager}} to the > {{JobManager}} if a {{TaskManager}} has died. That way, we can react faster > to {{TaskManager}} failures and recover our running job/s. -- This message was sent by Atlassian JIRA (v7.6.3#76005)