hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4274) NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before
Date Fri, 16 Oct 2015 16:46:05 GMT

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

Junping Du updated YARN-4274:
-----------------------------
    Description: 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.  (was:
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 times failure in registering to RM.)

> 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