[jira] [Updated] (YARN-10970) Prometheussink: Standby RM should expose prom endpoint

[ https://issues.apache.org/jira/browse/YARN-10970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10970: -- Labels: pull-request-available (was: ) > Prometheussink: Standby RM should expose prom

[jira] [Commented] (YARN-10966) nodeUpdate will make NPE when node decomissioning trans to decomissed at same time

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

[jira] [Commented] (YARN-10970) Prometheussink: Standby RM should expose prom endpoint

[ https://issues.apache.org/jira/browse/YARN-10970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419680#comment-17419680 ] Max Xie commented on YARN-10970: - PR :  https://github.com/apache/hadoop/pull/3480 > Prometheussink:

[jira] [Created] (YARN-10970) Prometheussink: Standby RM should expose prom endpoint

Max Xie created YARN-10970: --- Summary: Prometheussink: Standby RM should expose prom endpoint Key: YARN-10970 URL: https://issues.apache.org/jira/browse/YARN-10970 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-10969) After RM fail-over, getContainerStatus fails from ApplicationMaster to NodeManager

[ https://issues.apache.org/jira/browse/YARN-10969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lee young gon updated YARN-10969: - Description: If the artifact type of yarn-service spec is docker, getContainerStatus is

[jira] [Updated] (YARN-10968) SchedulingRequests can be wrong when multiple containers stopped at the same time

[ https://issues.apache.org/jira/browse/YARN-10968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lee young gon updated YARN-10968: - Attachment: (was: YARN-10968.001.patch) > SchedulingRequests can be wrong when multiple

[jira] [Updated] (YARN-10966) nodeUpdate will make NPE when node decomissioning trans to decomissed at same time

[ https://issues.apache.org/jira/browse/YARN-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuyu updated YARN-10966: Attachment: (was: YARN-10966.001.patch) > nodeUpdate will make NPE when node decomissioning trans to

[jira] [Commented] (YARN-10969) After RM fail-over, getContainerStatus fails from ApplicationMaster to NodeManager

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

[jira] [Commented] (YARN-10968) SchedulingRequests can be wrong when multiple containers stopped at the same time

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

[jira] [Updated] (YARN-10968) SchedulingRequests can be wrong when multiple containers stopped at the same time

[ https://issues.apache.org/jira/browse/YARN-10968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lee young gon updated YARN-10968: - Attachment: YARN-10968.002.patch > SchedulingRequests can be wrong when multiple containers