[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267224#comment-16267224 ] Hudson commented on YARN-6168: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13279 (See

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267191#comment-16267191 ] Chandni Singh commented on YARN-6168: - Thanks [~jianhe] > Restarted RM may not inform AM about all

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267181#comment-16267181 ] Jian He commented on YARN-6168: --- I committed this into trunk. Thanks [~csingh] ! > Restarted RM may not

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267173#comment-16267173 ] Chandni Singh commented on YARN-6168: - Test and findbug failure are not related to the change >

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261794#comment-16261794 ] Hadoop QA commented on YARN-6168: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261678#comment-16261678 ] Hadoop QA commented on YARN-6168: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261552#comment-16261552 ] Jian He commented on YARN-6168: --- A minor optimization for pullPreviousAttemptContainers : we could add a

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260204#comment-16260204 ] Hadoop QA commented on YARN-6168: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259960#comment-16259960 ] Jian He commented on YARN-6168: --- could you also add more detailed comments in

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259957#comment-16259957 ] Jian He commented on YARN-6168: --- - AllocateResponsePBImpl#mergeLocalToBuilder needs some changes too ? -

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259697#comment-16259697 ] Chandni Singh commented on YARN-6168: - [~billie.rinaldi] [~jianhe] Can you please review > Restarted

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256357#comment-16256357 ] Hadoop QA commented on YARN-6168: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16246744#comment-16246744 ] Chandni Singh commented on YARN-6168: - The default value of {{nmExpiryInterval}} is 10 minutes. That

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146075#comment-16146075 ] Jian He commented on YARN-6168: --- Probably one way would be to change the AM heartbeat to also return previous

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947326#comment-15947326 ] Jason Lowe commented on YARN-6168: -- This sounds like the RM isn't waiting long enough for all the live NMs

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947305#comment-15947305 ] Billie Rinaldi commented on YARN-6168: -- Yes. In my case, the AM requested new containers immediately

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946721#comment-15946721 ] Shen Yinjie commented on YARN-6168: --- the case happened few times after restartedafter more