[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-117: - Attachment: YARN-117-025.patch Enhance YARN service model

[jira] [Commented] (YARN-801) Expose container locations and capabilities in the RM REST APIs

[ https://issues.apache.org/jira/browse/YARN-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681944#comment-13681944 ] Sandy Ryza commented on YARN-801: - [~djp], you're right, we should include ContainerState as

[jira] [Commented] (YARN-588) Two identical utility methods in different classes to build Resource

[ https://issues.apache.org/jira/browse/YARN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681947#comment-13681947 ] Sandy Ryza commented on YARN-588: - Thanks for the patch, Niranjan! Since I filed this JIRA,

[jira] [Commented] (YARN-800) Clicking on an AM link for a running app leads to a HTTP 500

[ https://issues.apache.org/jira/browse/YARN-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681954#comment-13681954 ] Jian He commented on YARN-800: -- The link is not broken in local cluster because by default

[jira] [Commented] (YARN-588) Two identical utility methods in different classes to build Resource

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

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681972#comment-13681972 ] Arun C Murthy commented on YARN-796: Yes, we'll need to add admin api (via rmadmin) to

[jira] [Commented] (YARN-117) Enhance YARN service model

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

[jira] [Commented] (YARN-117) Enhance YARN service model

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

[jira] [Commented] (YARN-801) Expose container locations and capabilities in the RM REST APIs

[ https://issues.apache.org/jira/browse/YARN-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682033#comment-13682033 ] Junping Du commented on YARN-801: - I mean if container is in running state, do we want to

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

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-291: Description: The current Hadoop YARN resource management logic assumes per node resource is static during

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-600) Hook up cgroups CPU settings to the number of virtual cores allocated

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

[jira] [Commented] (YARN-648) FS: Add documentation for pluggable policy

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

[jira] [Commented] (YARN-700) TestInfoBlock fails on Windows because of line ending missmatch

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

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

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682124#comment-13682124 ] Junping Du commented on YARN-291: - Hi [~tucu00], thanks for comments above. Actually, just

[jira] [Commented] (YARN-588) Two identical utility methods in different classes to build Resource

[ https://issues.apache.org/jira/browse/YARN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682126#comment-13682126 ] Niranjan Singh commented on YARN-588: - Hi Sandy, Thanks for the comments , I agree

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-600) Hook up cgroups CPU settings to the number of virtual cores allocated

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

[jira] [Commented] (YARN-648) FS: Add documentation for pluggable policy

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

[jira] [Commented] (YARN-700) TestInfoBlock fails on Windows because of line ending missmatch

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

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

[ https://issues.apache.org/jira/browse/YARN-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682230#comment-13682230 ] Alejandro Abdelnur commented on YARN-789: - [~acmurthy], I assume you refer to the

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682247#comment-13682247 ] Alejandro Abdelnur commented on YARN-796: - bq. Yes, we'll need to add admin api (via

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-600) Hook up cgroups CPU settings to the number of virtual cores allocated

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

[jira] [Commented] (YARN-648) FS: Add documentation for pluggable policy

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

[jira] [Commented] (YARN-700) TestInfoBlock fails on Windows because of line ending missmatch

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

[jira] [Created] (YARN-802) APPLICATION_INIT is never sent to AuxServices other than the builtin ShuffleHandler

Avner BenHanoch created YARN-802: Summary: APPLICATION_INIT is never sent to AuxServices other than the builtin ShuffleHandler Key: YARN-802 URL: https://issues.apache.org/jira/browse/YARN-802

[jira] [Updated] (YARN-802) APPLICATION_INIT is never sent to AuxServices other than the builtin ShuffleHandler

[ https://issues.apache.org/jira/browse/YARN-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avner BenHanoch updated YARN-802: - Description: APPLICATION_INIT is never sent to AuxServices other than the built-in

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682323#comment-13682323 ] Alejandro Abdelnur commented on YARN-796: - One thing I forgot to mention before is

[jira] [Commented] (YARN-801) Expose container locations and capabilities in the RM REST APIs

[ https://issues.apache.org/jira/browse/YARN-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682342#comment-13682342 ] Alejandro Abdelnur commented on YARN-801: - Traversing the scheduler data structures

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

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682361#comment-13682361 ] Alejandro Abdelnur commented on YARN-291: - [~djp], yes that should do it, at least

[jira] [Commented] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

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

[jira] [Commented] (YARN-117) Enhance YARN service model

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

[jira] [Commented] (YARN-588) Two identical utility methods in different classes to build Resource

[ https://issues.apache.org/jira/browse/YARN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682395#comment-13682395 ] Sandy Ryza commented on YARN-588: - I meant that neither Resources#createResource nor

[jira] [Commented] (YARN-588) Two identical utility methods in different classes to build Resource

[ https://issues.apache.org/jira/browse/YARN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682398#comment-13682398 ] Sandy Ryza commented on YARN-588: - *so many *names* that sound so similar

[jira] [Created] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

Alejandro Abdelnur created YARN-803: --- Summary: factor out scheduler config validation from the ResourceManager to each scheduler implementation Key: YARN-803 URL: https://issues.apache.org/jira/browse/YARN-803

[jira] [Updated] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-803: Attachment: YARN-803.patch patch moving conf validation to the setConf() method of the

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

[ https://issues.apache.org/jira/browse/YARN-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682409#comment-13682409 ] Alejandro Abdelnur commented on YARN-789: - Created YARN-803 to factor out conf

[jira] [Commented] (YARN-801) Expose container locations and capabilities in the RM REST APIs

[ https://issues.apache.org/jira/browse/YARN-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682403#comment-13682403 ] Sandy Ryza commented on YARN-801: - As YARN is agnostic to what its containers are used for,

[jira] [Resolved] (YARN-125) Make Yarn Client service shutdown operations robust

[ https://issues.apache.org/jira/browse/YARN-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-125. - Resolution: Fixed Fix Version/s: 2.1.0-beta Make Yarn Client service shutdown

[jira] [Resolved] (YARN-123) Make yarn Resource Manager services robust against shutdown

[ https://issues.apache.org/jira/browse/YARN-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-123. - Resolution: Fixed Fix Version/s: 2.1.0-beta Make yarn Resource Manager services robust

[jira] [Resolved] (YARN-124) Make Yarn Node Manager services robust against shutdown

[ https://issues.apache.org/jira/browse/YARN-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-124. - Resolution: Fixed Fix Version/s: 2.1.0-beta Make Yarn Node Manager services robust

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

[ https://issues.apache.org/jira/browse/YARN-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682424#comment-13682424 ] Bikas Saha commented on YARN-789: - Do the resource calculator changes need to be considered

[jira] [Created] (YARN-804) mark AbstractService init/start/stop methods as final

Steve Loughran created YARN-804: --- Summary: mark AbstractService init/start/stop methods as final Key: YARN-804 URL: https://issues.apache.org/jira/browse/YARN-804 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

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

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682444#comment-13682444 ] Zhijie Shen commented on YARN-803: -- It sounds a good idea to support polymorphy of config

[jira] [Created] (YARN-805) Fix yarn-api javadoc annotations

Jian He created YARN-805: Summary: Fix yarn-api javadoc annotations Key: YARN-805 URL: https://issues.apache.org/jira/browse/YARN-805 Project: Hadoop YARN Issue Type: Bug Reporter: Jian

[jira] [Commented] (YARN-746) rename Service.register() and Service.unregister() to registerServiceListener() unregisterServiceListener() respectively

[ https://issues.apache.org/jira/browse/YARN-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682459#comment-13682459 ] Vinod Kumar Vavilapalli commented on YARN-746: -- Looks good. +1. Checking this

[jira] [Commented] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682458#comment-13682458 ] Omkar Vinit Joshi commented on YARN-692: rebasing after YARN-117

[jira] [Updated] (YARN-804) mark AbstractService init/start/stop methods as final

[ https://issues.apache.org/jira/browse/YARN-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-804: - Issue Type: Sub-task (was: Improvement) Parent: YARN-117 mark

[jira] [Commented] (YARN-746) rename Service.register() and Service.unregister() to registerServiceListener() unregisterServiceListener() respectively

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

[jira] [Commented] (YARN-805) Fix yarn-api javadoc annotations

[ https://issues.apache.org/jira/browse/YARN-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682478#comment-13682478 ] Jian He commented on YARN-805: -- Proposal to fix annotations for yarn api as: 1. for all

[jira] [Assigned] (YARN-804) mark AbstractService init/start/stop methods as final

[ https://issues.apache.org/jira/browse/YARN-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-804: Assignee: Vinod Kumar Vavilapalli Let me take a quick stab at it to get it

[jira] [Updated] (YARN-805) Fix yarn-api javadoc annotations

[ https://issues.apache.org/jira/browse/YARN-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-805: - Issue Type: Sub-task (was: Bug) Parent: YARN-386 Fix yarn-api javadoc annotations

[jira] [Commented] (YARN-802) APPLICATION_INIT is never sent to AuxServices other than the builtin ShuffleHandler

[ https://issues.apache.org/jira/browse/YARN-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682488#comment-13682488 ] Siddharth Seth commented on YARN-802: - Can the MR AM specify the service to be used via

[jira] [Created] (YARN-806) Move ContainerExitStatus from yarn.api to yarn.api.records

Jian He created YARN-806: Summary: Move ContainerExitStatus from yarn.api to yarn.api.records Key: YARN-806 URL: https://issues.apache.org/jira/browse/YARN-806 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Attachment: YARN-692-20130613.patch Creating NMToken master key on RM and sharing

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682495#comment-13682495 ] Alejandro Abdelnur commented on YARN-803: - Zhijie, On adding the setConf() method

[jira] [Created] (YARN-807) When querying apps by queue, iterating over all apps is inefficient and limiting

Sandy Ryza created YARN-807: --- Summary: When querying apps by queue, iterating over all apps is inefficient and limiting Key: YARN-807 URL: https://issues.apache.org/jira/browse/YARN-807 Project: Hadoop

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682503#comment-13682503 ] Sandy Ryza commented on YARN-803: - A Configuration already gets passed in when a scheduler's

[jira] [Updated] (YARN-736) Add a multi-resource fair sharing metric

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-736: Attachment: YARN-736.patch Add a multi-resource fair sharing metric

[jira] [Commented] (YARN-802) APPLICATION_INIT is never sent to AuxServices other than the builtin ShuffleHandler

[ https://issues.apache.org/jira/browse/YARN-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682539#comment-13682539 ] Avner BenHanoch commented on YARN-802: -- Hi Siddharth, I am not sure I understand the

[jira] [Commented] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12587673/YARN-692-20130613.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include

[jira] [Updated] (YARN-693) Sending NMToken to AM on allocate call

[ https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-693: --- Attachment: YARN-693-20130613.patch rebasing patch after YARN-117 Sending

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

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

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682564#comment-13682564 ] Alejandro Abdelnur commented on YARN-803: - mmh, so i guess we could do a mix of what

[jira] [Updated] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

[ https://issues.apache.org/jira/browse/YARN-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-773: - Attachment: YARN-773.1.patch rebased after YARN-117 Move YarnRuntimeException from package

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682565#comment-13682565 ] Arun C Murthy commented on YARN-796: bq. One thing I forgot to mention before is that

[jira] [Commented] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682571#comment-13682571 ] Chris Douglas commented on YARN-569: Thanks for the feedback; we revised the patch. We

[jira] [Created] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

Bikas Saha created YARN-808: --- Summary: ApplicationReport does not clearly tell that the attempt is running or not Key: YARN-808 URL: https://issues.apache.org/jira/browse/YARN-808 Project: Hadoop YARN

[jira] [Moved] (YARN-809) Enable better parallelism in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza moved MAPREDUCE-5321 to YARN-809: Key: YARN-809 (was: MAPREDUCE-5321) Project: Hadoop YARN (was:

[jira] [Updated] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-803: Attachment: YARN-803.patch patch integrating feedback from Zhijie and Sandy as per my

[jira] [Commented] (YARN-809) Enable better parallelism in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682595#comment-13682595 ] Alejandro Abdelnur commented on YARN-809: - One thing to keep in mind is that if

[jira] [Updated] (YARN-804) mark AbstractService init/start/stop methods as final

[ https://issues.apache.org/jira/browse/YARN-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-804: Attachment: YARN-804-001.patch Marking the methods as final, and fixing a (recent) test that needs

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682619#comment-13682619 ] Sandy Ryza commented on YARN-803: - Would it make sense to put validateConf in

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682636#comment-13682636 ] Sandy Ryza commented on YARN-803: - +1 factor out scheduler config

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682634#comment-13682634 ] Alejandro Abdelnur commented on YARN-803: - Sandhy, SchedulerUtils is for all

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682635#comment-13682635 ] Sandy Ryza commented on YARN-803: - Ok, makes sense. factor out scheduler

[jira] [Updated] (YARN-789) Enable zero capabilities resource requests in fair scheduler

[ https://issues.apache.org/jira/browse/YARN-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-789: Attachment: YARN-789.patch [~bikassaha], FS uses ResourceCalculator methods to normalize

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

[ https://issues.apache.org/jira/browse/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682652#comment-13682652 ] Zhijie Shen commented on YARN-803: -- looks good. +1 factor out scheduler

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

[ https://issues.apache.org/jira/browse/YARN-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682656#comment-13682656 ] Alejandro Abdelnur commented on YARN-789: - btw, the current patch requires YARN-803.

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

Chris Riccomini created YARN-810: Summary: Support CGroup ceiling enforcement on CPU Key: YARN-810 URL: https://issues.apache.org/jira/browse/YARN-810 Project: Hadoop YARN Issue Type: Bug

[jira] [Assigned] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reassigned YARN-379: - Assignee: Ravi Prakash (was: Abhishek Kapoor) yarn [node,application] command print logger

[jira] [Commented] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682666#comment-13682666 ] Ravi Prakash commented on YARN-379: --- Hi Abhishek! Thanks for the contribution. I can help

[jira] [Commented] (YARN-773) Move YarnRuntimeException from package api.yarn to api.yarn.exceptions

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

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

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Riccomini updated YARN-810: - Description: Problem statement: YARN currently lets you define an NM's pcore count, and a

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

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Riccomini updated YARN-810: - Description: Problem statement: YARN currently lets you define an NM's pcore count, and a

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

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Riccomini updated YARN-810: - Description: Problem statement: YARN currently lets you define an NM's pcore count, and a

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

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Riccomini updated YARN-810: - Description: Problem statement: YARN currently lets you define an NM's pcore count, and a

[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=13682677#comment-13682677 ] Sandy Ryza commented on YARN-810: - [~criccomini], I'm intending to remove the vcore-pcore

[jira] [Updated] (YARN-736) Add a multi-resource fair sharing metric

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-736: Attachment: YARN-736-1.patch Add a multi-resource fair sharing metric

[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=13682684#comment-13682684 ] Sandy Ryza commented on YARN-810: - a configurable % ceiling I mean.

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682689#comment-13682689 ] Sandy Ryza commented on YARN-736: - Attached an updated patch that takes maximum shares into

[jira] [Updated] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

[ https://issues.apache.org/jira/browse/YARN-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated YARN-799: Description: The implementation of bq.

[jira] [Commented] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

[ https://issues.apache.org/jira/browse/YARN-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682698#comment-13682698 ] Adar Dembo commented on YARN-799: - Thread group IDs should be written to /cgroup.procs while

[jira] [Commented] (YARN-804) mark AbstractService init/start/stop methods as final

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

[jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation

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

[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=13682710#comment-13682710 ] Chris Riccomini commented on YARN-810: -- Hey Sandy, If I understand you correctly, not

[jira] [Commented] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

[ https://issues.apache.org/jira/browse/YARN-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682715#comment-13682715 ] Chris Riccomini commented on YARN-799: -- Hey Adar, Thanks, this is super useful. In the

  1   2   >