[jira] [Commented] (YARN-370) CapacityScheduler app submission fails when min alloc size not multiple of AM size

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

[jira] [Commented] (YARN-370) CapacityScheduler app submission fails when min alloc size not multiple of AM size

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

[jira] [Commented] (YARN-370) CapacityScheduler app submission fails when min alloc size not multiple of AM size

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

[jira] [Updated] (YARN-382) SchedulerUtils improve way normalizeRequest sets the resource capabilities

[ https://issues.apache.org/jira/browse/YARN-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-382: --- Description: In YARN-370, we changed it from setting the capability to directly setting memory and

[jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers

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

[jira] [Commented] (YARN-357) App submission should not be synchronized

[ https://issues.apache.org/jira/browse/YARN-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572545#comment-13572545 ] Hadoop QA commented on YARN-357: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-355) RM app submission jams under load

[ https://issues.apache.org/jira/browse/YARN-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated YARN-355: - Attachment: YARN-355.patch YARN-355.branch-23.patch Thanks Sid. Updated patches to set

[jira] [Updated] (YARN-355) RM app submission jams under load

[ https://issues.apache.org/jira/browse/YARN-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-355: --- Target Version/s: 2.0.3-alpha, 0.23.7 (was: 2.0.3-alpha, 0.23.6) RM app submission jams under

[jira] [Updated] (YARN-383) AMRMClientImpl should handle null rmClient in stop()

[ https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-383: - Attachment: YARN-383.1.patch Trivial patch. AMRMClientImpl should handle null rmClient

[jira] [Updated] (YARN-40) Provide support for missing yarn commands

[ https://issues.apache.org/jira/browse/YARN-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-40: -- Fix Version/s: 0.23.7 Provide support for missing yarn commands

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Updated patch for branch-0.23 Capacity

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Updated patch for trunk Capacity Scheduler web page should

[jira] [Commented] (YARN-355) RM app submission jams under load

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

[jira] [Updated] (YARN-150) AppRejectedTransition does not unregister app from master service and scheduler

[ https://issues.apache.org/jira/browse/YARN-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-150: --- Fix Version/s: 0.23.7 AppRejectedTransition does not unregister app from master service and

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Updated docs to include active and pending applications

[jira] [Commented] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572709#comment-13572709 ] Ravi Prakash commented on YARN-249: --- Thanks a lot for your review Tom! I've incorporated

[jira] [Commented] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572742#comment-13572742 ] Hadoop QA commented on YARN-249: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-383) AMRMClientImpl should handle null rmClient in stop()

[ https://issues.apache.org/jira/browse/YARN-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572892#comment-13572892 ] Hadoop QA commented on YARN-383: {color:red}-1 overall{color}. Here are the results of

[jira] [Created] (YARN-385) ResourceRequestPBImpl's toString() is missing location and # containers

Sandy Ryza created YARN-385: --- Summary: ResourceRequestPBImpl's toString() is missing location and # containers Key: YARN-385 URL: https://issues.apache.org/jira/browse/YARN-385 Project: Hadoop YARN

[jira] [Resolved] (YARN-359) NodeManager container-related tests fail on branch-trunk-win

[ https://issues.apache.org/jira/browse/YARN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-359. -- Resolution: Fixed I just committed this to branch-trunk-win. Thanks Chris!

[jira] [Commented] (YARN-359) NodeManager container-related tests fail on branch-trunk-win

[ https://issues.apache.org/jira/browse/YARN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573116#comment-13573116 ] Bikas Saha commented on YARN-359: - The main reason for moving these to Shell was to reduce

[jira] [Updated] (YARN-20) More information for yarn.resourcemanager.webapp.address in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nemon lou updated YARN-20: -- Attachment: YARN-20.patch Adding annotation just as Harsh J said.Sorry for comming back so late.No test case is

[jira] [Commented] (YARN-111) Application level priority in Resource Manager Schedulers

[ https://issues.apache.org/jira/browse/YARN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573142#comment-13573142 ] nemon lou commented on YARN-111: Finally i use two Queues in Capacity Scheduler to basically

[jira] [Updated] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-362: -- Attachment: YARN-362.branch-0.23.patch Thanks for the review Jason! I hadn't realized that I hadn't

[jira] [Updated] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-362: -- Attachment: YARN-362.patch The patch ported to trunk Unexpected extra results when

[jira] [Commented] (YARN-111) Application level priority in Resource Manager Schedulers

[ https://issues.apache.org/jira/browse/YARN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573157#comment-13573157 ] Vinod Kumar Vavilapalli commented on YARN-111: -- So, can we close this as won't

[jira] [Commented] (YARN-374) Job History Server doesn't show jobs which killed by ClientRMProtocol.forceKillApplication

[ https://issues.apache.org/jira/browse/YARN-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573165#comment-13573165 ] nemon lou commented on YARN-374: Thanks for the information. But why not have one more API

[jira] [Commented] (YARN-359) NodeManager container-related tests fail on branch-trunk-win

[ https://issues.apache.org/jira/browse/YARN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573166#comment-13573166 ] Vinod Kumar Vavilapalli commented on YARN-359: -- bq. The main reason for moving

[jira] [Commented] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573168#comment-13573168 ] Hadoop QA commented on YARN-362: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-236) RM should point tracking URL to RM web page when app fails to start

[ https://issues.apache.org/jira/browse/YARN-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573184#comment-13573184 ] Vinod Kumar Vavilapalli commented on YARN-236: -- I agree that the null check can

[jira] [Commented] (YARN-359) NodeManager container-related tests fail on branch-trunk-win

[ https://issues.apache.org/jira/browse/YARN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573183#comment-13573183 ] Chris Nauroth commented on YARN-359: Thanks for the commit. Sorry, Bikas. I had

[jira] [Commented] (YARN-209) Capacity scheduler can leave application in pending state

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573188#comment-13573188 ] Vinod Kumar Vavilapalli commented on YARN-209: -- Haven't looked at the code yet,

[jira] [Created] (YARN-387) Fix inconsistent protocol naming

Vinod Kumar Vavilapalli created YARN-387: Summary: Fix inconsistent protocol naming Key: YARN-387 URL: https://issues.apache.org/jira/browse/YARN-387 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-387: - Labels: incompatible (was: ) This is going to be an incompatible change for

[jira] [Commented] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573206#comment-13573206 ] Vinod Kumar Vavilapalli commented on YARN-387: -- I propose we do the following

[jira] [Commented] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573234#comment-13573234 ] Sandy Ryza commented on YARN-387: - +1 to the proposal If I understand the RMAdminProtocol

[jira] [Commented] (YARN-374) Job History Server doesn't show jobs which killed by ClientRMProtocol.forceKillApplication

[ https://issues.apache.org/jira/browse/YARN-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573238#comment-13573238 ] nemon lou commented on YARN-374: Agree that YARN-321 will help. Job

[jira] [Commented] (YARN-365) Each NM heartbeat should not generate and event for the Scheduler

[ https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573244#comment-13573244 ] Siddharth Seth commented on YARN-365: - This isn't very different from configuring all

[jira] [Commented] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573273#comment-13573273 ] Karthik Kambatla commented on YARN-387: --- Good idea! Fix inconsistent