[jira] [Created] (YARN-3915) scmadmin help message correction

Bibin A Chundatt created YARN-3915: -- Summary: scmadmin help message correction Key: YARN-3915 URL: https://issues.apache.org/jira/browse/YARN-3915 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3915) scmadmin help message correction

[ https://issues.apache.org/jira/browse/YARN-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3915: --- Description: Help message for scmadmin *Actual* {{hadoop scmadmin}} *expected* {{yarn

[jira] [Created] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

Varun Saxena created YARN-3916: -- Summary: DrainDispatcher#await should wait till event has been completely handled Key: YARN-3916 URL: https://issues.apache.org/jira/browse/YARN-3916 Project: Hadoop

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623362#comment-14623362 ] Varun Saxena commented on YARN-3916: In YARN-3878 we introduced check for whether event

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623343#comment-14623343 ] Hudson commented on YARN-3445: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #253 (See

[jira] [Updated] (YARN-3915) scmadmin help message correction

[ https://issues.apache.org/jira/browse/YARN-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3915: --- Attachment: 0001-YARN-3915.patch Patch attached for bug please review scmadmin help message

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623344#comment-14623344 ] Hudson commented on YARN-3116: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #253 (See

[jira] [Commented] (YARN-3656) LowCost: A Cost-Based Placement Agent for YARN Reservations

[ https://issues.apache.org/jira/browse/YARN-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623300#comment-14623300 ] Arun Suresh commented on YARN-3656: --- [~jyaniv], [~curino] and [~imenache], This looks

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623348#comment-14623348 ] Hudson commented on YARN-3116: -- FAILURE: Integrated in Hadoop-Yarn-trunk #983 (See

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623347#comment-14623347 ] Hudson commented on YARN-3445: -- FAILURE: Integrated in Hadoop-Yarn-trunk #983 (See

[jira] [Updated] (YARN-3910) TestRMAppTransitions#testAppAcceptedAttemptKilled fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3910: --- Attachment: YARN-3910.02.patch [~adhoot], updated patch after addressing your comments

[jira] [Commented] (YARN-3910) TestRMAppTransitions#testAppAcceptedAttemptKilled fails on trunk

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

[jira] [Commented] (YARN-3898) YARN web console only proxies GET to application master but doesn't provide any feedback for other HTTP methods

[ https://issues.apache.org/jira/browse/YARN-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623430#comment-14623430 ] Steve Loughran commented on YARN-3898: -- YARN-2084 covers not filtering the other

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623384#comment-14623384 ] Hudson commented on YARN-3445: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #251 (See

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623385#comment-14623385 ] Hudson commented on YARN-3116: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #251 (See

[jira] [Commented] (YARN-3898) YARN web console only proxies GET to application master but doesn't provide any feedback for other HTTP methods

[ https://issues.apache.org/jira/browse/YARN-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623456#comment-14623456 ] Kam Kasravi commented on YARN-3898: --- Yes - should i mark this as a duplicate? On

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623458#comment-14623458 ] Hudson commented on YARN-3116: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2199 (See

[jira] [Commented] (YARN-3644) Node manager shuts down if unable to connect with RM

[ https://issues.apache.org/jira/browse/YARN-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623462#comment-14623462 ] Raju Bairishetti commented on YARN-3644: Thanks [~varun_saxena] for the review and

[jira] [Commented] (YARN-2031) YARN Proxy model doesn't support REST APIs in AMs

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

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623457#comment-14623457 ] Hudson commented on YARN-3445: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2199 (See

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623391#comment-14623391 ] Hudson commented on YARN-3116: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2180 (See

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623390#comment-14623390 ] Hudson commented on YARN-3445: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2180 (See

[jira] [Commented] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623415#comment-14623415 ] Hudson commented on YARN-3116: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #241 (See

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

[ https://issues.apache.org/jira/browse/YARN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623414#comment-14623414 ] Hudson commented on YARN-3445: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #241 (See

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623498#comment-14623498 ] Sunil G commented on YARN-3894: --- HI [~leftnoteasy] Thank you for sharing your thoughts. +1

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623499#comment-14623499 ] Sunil G commented on YARN-3849: --- Thank you very much [~leftnoteasy] for reviewing and

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623489#comment-14623489 ] Wangda Tan commented on YARN-3894: -- Hi [~bibinchundatt], Are you using latest trunk? In

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623497#comment-14623497 ] Hudson commented on YARN-3849: -- FAILURE: Integrated in Hadoop-trunk-Commit #8151 (See

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623508#comment-14623508 ] Bibin A Chundatt commented on YARN-3894: Hi [~leftnoteasy] Thank you for sharing

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623527#comment-14623527 ] Bibin A Chundatt commented on YARN-3894: [~sunilg] and [~leftnoteasy] Please review

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623491#comment-14623491 ] Wangda Tan commented on YARN-3894: -- After read comment from [~sunilg], I know what's the

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623494#comment-14623494 ] Wangda Tan commented on YARN-3849: -- Latest patch LGTM, committing. Too much of

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623502#comment-14623502 ] Sunil G commented on YARN-3893: --- refreshAll() is doing many set of refresh operations. And

[jira] [Updated] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3894: --- Attachment: 0001-YARN-3894.patch Attached patch as per discussion. Please review patch RM

[jira] [Resolved] (YARN-2007) AM expressing the estimated endtime to RM

[ https://issues.apache.org/jira/browse/YARN-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maysam Yabandeh resolved YARN-2007. --- Resolution: Not A Problem AM expressing the estimated endtime to RM

[jira] [Commented] (YARN-3910) TestRMAppTransitions#testAppAcceptedAttemptKilled fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623617#comment-14623617 ] Anubhav Dhoot commented on YARN-3910: - LGTM. Tried out the changes and even if I force

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

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

[jira] [Commented] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623590#comment-14623590 ] Varun Saxena commented on YARN-3916: Pre YARN-3878 code would have actually worked for

[jira] [Commented] (YARN-3894) RM startup should fail for wrong CS xml NodeLabel capacity configuration

[ https://issues.apache.org/jira/browse/YARN-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623566#comment-14623566 ] Bibin A Chundatt commented on YARN-3894: Testcase failures are not due of this

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623567#comment-14623567 ] Varun Saxena commented on YARN-3893: [~sunilg] We can do the cleanup(i.e. stop active

[jira] [Updated] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3916: --- Attachment: YARN-3916.01.patch Updated patch DrainDispatcher#await should wait till event has been

[jira] [Updated] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3916: --- Attachment: (was: YARN-3916.01.patch) DrainDispatcher#await should wait till event has been

[jira] [Updated] (YARN-3916) DrainDispatcher#await should wait till event has been completely handled

[ https://issues.apache.org/jira/browse/YARN-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3916: --- Attachment: YARN-3916.01.patch DrainDispatcher#await should wait till event has been completely

[jira] [Commented] (YARN-3644) Node manager shuts down if unable to connect with RM

[ https://issues.apache.org/jira/browse/YARN-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623616#comment-14623616 ] Varun Saxena commented on YARN-3644: [~raju.bairishetti], bq. I ran the test in

[jira] [Moved] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all excpetions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gera Shegalov moved HADOOP-1 to YARN-3917: -- Affects Version/s: (was: 2.8.0) 2.8.0

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all excpetions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623663#comment-14623663 ] Gera Shegalov commented on YARN-3917: - Thanks [~chris.douglas] for review. Moved JIRA

[jira] [Updated] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gera Shegalov updated YARN-3917: Summary: getResourceCalculatorPlugin for the default should intercept all exceptions (was:

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

[ https://issues.apache.org/jira/browse/YARN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623673#comment-14623673 ] Hudson commented on YARN-3917: -- FAILURE: Integrated in Hadoop-trunk-Commit #8152 (See

[jira] [Commented] (YARN-3917) getResourceCalculatorPlugin for the default should intercept all exceptions

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

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623676#comment-14623676 ] Varun Saxena commented on YARN-3893: For 2nd option, we will have to return STANDBY to