[jira] [Commented] (YARN-1048) Add new AMRMClientAsync.getMatchingRequests method taking a Container as parameter

[ https://issues.apache.org/jira/browse/YARN-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740731#comment-13740731 ] Hitesh Shah commented on YARN-1048: --- [~josephkniest] That would be

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740735#comment-13740735 ] Bikas Saha commented on YARN-1004: -- IMO the intent of yarn.scheduler.max is to be an admin

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: (was: yarn-1044.patch) used/min/max resources do not display info in the scheduler

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch used/min/max resources do not display info in the scheduler page

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: (was: yarn-1044.patch) used/min/max resources do not display info in the scheduler

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch used/min/max resources do not display info in the scheduler page

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Updated] (YARN-1045) Improve toString implementation for PBImpls

[ https://issues.apache.org/jira/browse/YARN-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1045: - Hadoop Flags: Reviewed Improve toString implementation for PBImpls

[jira] [Commented] (YARN-1045) Improve toString implementation for PBImpls

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

[jira] [Commented] (YARN-337) RM handles killed application tracking URL poorly

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

[jira] [Commented] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

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

[jira] [Commented] (YARN-1045) Improve toString implementation for PBImpls

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

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740880#comment-13740880 ] nemon lou commented on YARN-292: FIFO Scheduler uses TreeMap to keep applications in FIFO

[jira] [Commented] (YARN-337) RM handles killed application tracking URL poorly

[ https://issues.apache.org/jira/browse/YARN-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740898#comment-13740898 ] Hudson commented on YARN-337: - FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #700 (See

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should be prefixed with the scheduler type

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740917#comment-13740917 ] Alejandro Abdelnur commented on YARN-1004: -- My motivation for this JIRA was that

[jira] [Commented] (YARN-337) RM handles killed application tracking URL poorly

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

[jira] [Commented] (YARN-1045) Improve toString implementation for PBImpls

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

[jira] [Commented] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

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

[jira] [Commented] (YARN-1045) Improve toString implementation for PBImpls

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

[jira] [Commented] (YARN-337) RM handles killed application tracking URL poorly

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

[jira] [Commented] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

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

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741051#comment-13741051 ] Arun C Murthy commented on YARN-1024: - [~sandyr] Thanks for taking the time to clearly

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741081#comment-13741081 ] Alejandro Abdelnur commented on YARN-1024: -- Instead cores, could we talk about

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741165#comment-13741165 ] Bikas Saha commented on YARN-1055: -- First of all, like folks have already agreed. This is

[jira] [Commented] (YARN-810) Support CGroup ceiling enforcement on CPU

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741170#comment-13741170 ] Robert Joseph Evans commented on YARN-810: -- Sorry I am a bit late to this

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741191#comment-13741191 ] Sandy Ryza commented on YARN-1024: -- bq. To paraphrase your proposal... Thanks for

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: (was: yarn-1044.patch) used/min/max resources do not display info in the scheduler

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch used/min/max resources do not display info in the scheduler page

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741213#comment-13741213 ] Arun C Murthy commented on YARN-1024: - bq. Correct me if I'm wrong, but you're talking

[jira] [Created] (YARN-1066) Improve toString implementation for PBImpls for AHS

Zhijie Shen created YARN-1066: - Summary: Improve toString implementation for PBImpls for AHS Key: YARN-1066 URL: https://issues.apache.org/jira/browse/YARN-1066 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741286#comment-13741286 ] Sangjin Lee commented on YARN-1044: --- I didn't add a new test because it is a small UI

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741289#comment-13741289 ] Sandy Ryza commented on YARN-1024: -- My opinion is that we shouldn't delay the release for

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741292#comment-13741292 ] Omkar Vinit Joshi commented on YARN-1044: - Thanks [~sjlee0] I would have liked to

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741309#comment-13741309 ] Sangjin Lee commented on YARN-1044: --- Hmm, do you want to just remove the element from the

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741318#comment-13741318 ] Omkar Vinit Joshi commented on YARN-1044: - Someone has already fixed it looks like

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741327#comment-13741327 ] Sangjin Lee commented on YARN-1044: --- Oh I see. The memory and vcores are there instead? I

[jira] [Updated] (YARN-1045) Improve toString implementation for PBImpls

[ https://issues.apache.org/jira/browse/YARN-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-1045: - Fix Version/s: (was: 2.1.1-beta) 2.1.0-beta Committed to

[jira] [Commented] (YARN-1045) Improve toString implementation for PBImpls

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

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741380#comment-13741380 ] Zhijie Shen commented on YARN-292: -- bq. FIFO Scheduler uses TreeMap to keep applications in

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741391#comment-13741391 ] Zhijie Shen commented on YARN-292: -- Sorry, just noticed that {code} // Try to assign

[jira] [Updated] (YARN-1065) NM should provide AuxillaryService data to the container

[ https://issues.apache.org/jira/browse/YARN-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1065: - Assignee: Xuan Gong NM should provide AuxillaryService data to the container

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044.patch Updated the patch to remove the unnecessary usedResources field.

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741450#comment-13741450 ] Omkar Vinit Joshi commented on YARN-1044: - Thanks [~sjlee0] .. just a small

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741460#comment-13741460 ] Sangjin Lee commented on YARN-1044: --- Oh OK... I've been following the suggestions in this

[jira] [Updated] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-881: - Attachment: YARN-881.patch Patch that change the compareTo method to return other.getPriority() -

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741468#comment-13741468 ] Omkar Vinit Joshi commented on YARN-1044: - I see.. yeah this is trivial.. I got

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741474#comment-13741474 ] Sangjin Lee commented on YARN-1044: --- It looks like some tests are broken. Let me look at

[jira] [Updated] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-897: --- Attachment: YARN-897-08152013-br-0.23.patch Posted patch for branch-0.23 CapacityScheduler

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741509#comment-13741509 ] Bikas Saha commented on YARN-881: - Fairly straight-foward change. Looks good to me. Jian,

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741511#comment-13741511 ] Jian He commented on YARN-881: -- All YARN tests passed locally , still running MR tests

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

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

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741515#comment-13741515 ] Sandy Ryza commented on YARN-881: - I'm OK with the change. Can testPriority to be renamed

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741518#comment-13741518 ] Robert Joseph Evans commented on YARN-1024: --- I am fine with that too.

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1044: -- Attachment: yarn-1044-20130815.3.patch used/min/max resources do not display info in the scheduler

[jira] [Commented] (YARN-1044) used/min/max resources do not display info in the scheduler page

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

[jira] [Updated] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-881: - Attachment: YARN-881.1.patch uploaded a new patch, fixed Sandy's comments Priority#compareTo

[jira] [Created] (YARN-1067) AMRMClient heartbeat interval should not be static

Siddharth Seth created YARN-1067: Summary: AMRMClient heartbeat interval should not be static Key: YARN-1067 URL: https://issues.apache.org/jira/browse/YARN-1067 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741713#comment-13741713 ] Luke Lu commented on YARN-291: -- It'll better if the node resource config is grouped into a

[jira] [Commented] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741717#comment-13741717 ] Kyle Leckie commented on YARN-1063: --- Hi Bikas, I have updated the Description of this

[jira] [Updated] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Leckie updated YARN-1063: -- Description: h1. Summary: Securing a Hadoop cluster requires constructing some form of security

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

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

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741777#comment-13741777 ] Jian He commented on YARN-881: -- MR tests also passed Priority#compareTo

[jira] [Commented] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741858#comment-13741858 ] Junping Du commented on YARN-291: - Hi [~vicaya] Thanks for suggestions. Yes. That should be

[jira] [Created] (YARN-1068) Implement YarnHAAdmin for HA specific admin operations

Karthik Kambatla created YARN-1068: -- Summary: Implement YarnHAAdmin for HA specific admin operations Key: YARN-1068 URL: https://issues.apache.org/jira/browse/YARN-1068 Project: Hadoop YARN