[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

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

2015-08-21 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.07.patch > RMNode transitioned from RUNNING to REBOOTED because its response id had not

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

2015-08-21 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: Attachment: 0001-YARN-3896.patch When I applying the patch, patch apply was failing for 2 chu

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

2015-07-23 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.06.patch > RMNode transitioned from RUNNING to REBOOTED because its response id had not

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

2015-07-20 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.05.patch > RMNode transitioned from RUNNING to REBOOTED because its response id had not

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

2015-07-10 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.04.patch Update patch to fix whitespace error. Failed test cases are not related. I will

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

2015-07-10 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.03.patch Attach a new path: add write lock to reset lastNodeHeartBeatResponse's ID. > RM

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

2015-07-09 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.02.patch > RMNode transitioned from RUNNING to REBOOTED because its response id had not

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

2015-07-08 Thread Devaraj K (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-3896: Target Version/s: 2.8.0 > RMNode transitioned from RUNNING to REBOOTED because its response id had not > bee

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

2015-07-08 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.01.patch Thanks [~devaraj.k] for the suggestion. Attach the patch as suggested. > RMNo

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

2015-07-08 Thread Jun Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Description: {noformat} 2015-07-03 16:49:39,075 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved 10.208