[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

2015-02-18 Thread Rohith (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Attachment: 0001-YARN-3194.patch > After NM restart, RM should handle NMCotainerStatuses sent by NM while > regist

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

2015-02-18 Thread Rohith (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Description: On NM restart ,NM sends all the outstanding NMContainerStatus to RM during registration. The registra

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

2015-02-18 Thread Rohith (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Description: On NM restart ,NM sends all the outstanding NMContainerStatus to RM during registration. The registra

[jira] [Updated] (YARN-3194) After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected node

2015-02-18 Thread Rohith (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3194: - Summary: After NM restart, RM should handle NMCotainerStatuses sent by NM while registering if NM is Reconnected no