[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.9.patch > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Jian He > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch, > YARN-479.4.patch, YARN-479.5.patch, YARN-479.6.patch, YARN-479.7.patch, > YARN-479.8.patch, YARN-479.9.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.8.patch Add test case that nodeStatusUpdater will retry a fixed number of time and eventually send SHUTDOWN to NM > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Jian He > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch, > YARN-479.4.patch, YARN-479.5.patch, YARN-479.6.patch, YARN-479.7.patch, > YARN-479.8.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.7.patch fix conflicts with YARN-101 > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Jian He > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch, > YARN-479.4.patch, YARN-479.5.patch, YARN-479.6.patch, YARN-479.7.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.6.patch > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Jian He > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch, > YARN-479.4.patch, YARN-479.5.patch, YARN-479.6.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.5.patch > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Jian He > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch, > YARN-479.4.patch, YARN-479.5.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-479: - Attachment: YARN-479.4.patch change while loop condition > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: jian he > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch, > YARN-479.4.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-479: - Attachment: YARN-479.3.patch > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: jian he > Attachments: YARN-479.1.patch, YARN-479.2.patch, YARN-479.3.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-479: - Attachment: YARN-479.2.patch > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: jian he > Attachments: YARN-479.1.patch, YARN-479.2.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-479: - Attachment: YARN-479.1.patch > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: jian he > Attachments: YARN-479.1.patch > > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats
[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-479: Assignee: jian he > NM retry behavior for connection to RM should be similar for lost heartbeats > > > Key: YARN-479 > URL: https://issues.apache.org/jira/browse/YARN-479 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: jian he > > Regardless of connection loss at the start or at an intermediate point, NM's > retry behavior to the RM should follow the same flow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
