hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4274) NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before
Date Mon, 26 Oct 2015 20:45:27 GMT

     [ https://issues.apache.org/jira/browse/YARN-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-4274:
------------------------------------------

We should try to merge this JIRA, YARN-4132, YARN-4288 together.

> NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen
before
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-4274
>                 URL: https://issues.apache.org/jira/browse/YARN-4274
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Junping Du
>            Assignee: Junping Du
>
> From YARN-3896, an non-fatal exception like response ID mismatch between NM and RM (due
to a race condition) will cause NM stop working. I think we should make it more robust to
tolerant a few failure in registering to RM with retry a few times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message