[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously

2017-01-05 Thread Junping Du (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3896: - Fix Version/s: 2.8.0 > RMNode transitioned from RUNNING to REBOOTED because its response id had not > been

[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously

2015-10-08 Thread Jason Lowe (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3896: - Fix Version/s: (was: 2.8.0) 2.6.2 2.7.2 I committed this to branc

[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously

2015-08-23 Thread Rohith Sharma K S (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3896: Labels: resourcemanager (was: ) > RMNode transitioned from RUNNING to REBOOTED because its r

[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously

2015-08-23 Thread Rohith Sharma K S (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3896: Summary: RMNode transitioned from RUNNING to REBOOTED because its response id had not been re