[jira] [Updated] (YARN-447) applicationComparator improvement for CS

[ https://issues.apache.org/jira/browse/YARN-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-447: --- Assignee: nemon lou > applicationComparator improvement for CS > --

[jira] [Commented] (YARN-447) applicationComparator improvement for CS

[ https://issues.apache.org/jira/browse/YARN-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618447#comment-13618447 ] Arun C Murthy commented on YARN-447: +1, lgtm! > applicationComparator

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618446#comment-13618446 ] Arun C Murthy commented on YARN-18: --- [~vicaya] / [~djp] - Can you please describe what is h

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

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618443#comment-13618443 ] Arun C Murthy commented on YARN-291: I commented on one of the sub-tasks, but I'm not co

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618433#comment-13618433 ] Arun C Murthy commented on YARN-412: [~theduderog] - No, you deserve credit for finding

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-412: --- Assignee: Roger Hoover (was: Arun C Murthy) > FifoScheduler incorrectly checking for node locality

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617340#comment-13617340 ] Arun C Murthy commented on YARN-460: +1, thanks Tom! > CS user left in

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614355#comment-13614355 ] Arun C Murthy commented on YARN-18: --- Sorry, I'm just getting to this. This is a lot to dige

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-412: --- Assignee: Roger Hoover > FifoScheduler incorrectly checking for node locality > ---

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598149#comment-13598149 ] Arun C Murthy commented on YARN-460: How about adding a 'error' or 'stopped' boolean or

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598148#comment-13598148 ] Arun C Murthy commented on YARN-460: Thomas - one thing that bothers me... Should we re

[jira] [Commented] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598147#comment-13598147 ] Arun C Murthy commented on YARN-462: Kendall - what sort of chargeback are you thinking

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597798#comment-13597798 ] Arun C Murthy commented on YARN-461: If the user specifically set the queue name to be e

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597586#comment-13597586 ] Arun C Murthy commented on YARN-461: Same for app name. > RMAppManager

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597584#comment-13597584 ] Arun C Murthy commented on YARN-461: Not sure this is correct. The default value for qu

[jira] [Commented] (YARN-450) Define value for * in the scheduling protocol

[ https://issues.apache.org/jira/browse/YARN-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595971#comment-13595971 ] Arun C Murthy commented on YARN-450: How about defining this in YarnConfiguration?

[jira] [Updated] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-449: --- Target Version/s: 2.0.4-alpha > MRAppMaster classpath not set properly for unit tests in downstream

[jira] [Updated] (YARN-429) capacity-scheduler config missing from yarn-test artifact

[ https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-429: --- Fix Version/s: (was: 2.0.5-beta) 2.0.4-alpha > capacity-scheduler config mis

[jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595872#comment-13595872 ] Arun C Murthy commented on YARN-449: [~yuzhih...@gmail.com] Thanks a bunch for helping u

[jira] [Commented] (YARN-443) allow OS scheduling priority of NM to be different than the containers it launches

[ https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594767#comment-13594767 ] Arun C Murthy commented on YARN-443: Thomas, wouldn't it be better to come from yarn-sit

[jira] [Commented] (YARN-408) Capacity Scheduler delay scheduling should not be disabled by default

[ https://issues.apache.org/jira/browse/YARN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594085#comment-13594085 ] Arun C Murthy commented on YARN-408: Looks good to me! Thanks Mayank. I'll re-kick huds

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

[ https://issues.apache.org/jira/browse/YARN-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587711#comment-13587711 ] Arun C Murthy commented on YARN-398: IAC, as I've said before: if it's the same proposal

[jira] [Commented] (YARN-429) capacity-scheduler config missing from yarn-test artifact

[ https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587564#comment-13587564 ] Arun C Murthy commented on YARN-429: This might have been caused by YARN-140, investigat

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

[ https://issues.apache.org/jira/browse/YARN-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587411#comment-13587411 ] Arun C Murthy commented on YARN-398: There are no details there. Furthermore it says: b

[jira] [Resolved] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved YARN-424. Resolution: Invalid Looks like we agree Bikas. I'm going to resolve this as won't fix. Please open s

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

[ https://issues.apache.org/jira/browse/YARN-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587149#comment-13587149 ] Arun C Murthy commented on YARN-398: Alejandro - not clear what you mean by option #1 in

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586579#comment-13586579 ] Arun C Murthy commented on YARN-392: Take a look at YARN-398 for a simpler alternate pro

[jira] [Commented] (YARN-398) Allow white-list and black-list of resources

[ https://issues.apache.org/jira/browse/YARN-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586576#comment-13586576 ] Arun C Murthy commented on YARN-398: Here is an approach I have a prelim patch on which

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586544#comment-13586544 ] Arun C Murthy commented on YARN-392: Also, we don't have to support *all* features in th

[jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586535#comment-13586535 ] Arun C Murthy commented on YARN-424: Also, the reason we have invested in using protobuf

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586529#comment-13586529 ] Arun C Murthy commented on YARN-392: Gang-scheduling, deadline-scheduling etc. are not *

[jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler

[ https://issues.apache.org/jira/browse/YARN-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586526#comment-13586526 ] Arun C Murthy commented on YARN-424: I'm not a fan of stringly-typed 'features' in the S

[jira] [Commented] (YARN-415) Capture memory utilization at the app-level for chargeback

[ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584667#comment-13584667 ] Arun C Murthy commented on YARN-415: +1 for the thought! > Capture memo

[jira] [Updated] (YARN-113) WebAppProxyServlet must use SSLFactory for the HttpClient connections

[ https://issues.apache.org/jira/browse/YARN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-113: --- Fix Version/s: (was: 2.0.3-alpha) 2.0.4-beta > WebAppProxyServlet must use S

[jira] [Updated] (YARN-322) Add cpu information to queue metrics

[ https://issues.apache.org/jira/browse/YARN-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-322: --- Fix Version/s: (was: 2.0.3-alpha) 2.0.4-beta > Add cpu information to queue

[jira] [Updated] (YARN-314) Schedulers should allow resource requests of different sizes at the same priority and location

[ https://issues.apache.org/jira/browse/YARN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-314: --- Fix Version/s: (was: 2.0.3-alpha) 2.0.4-beta > Schedulers should allow resou

[jira] [Updated] (YARN-308) Improve documentation about what "asks" means in AMRMProtocol

[ https://issues.apache.org/jira/browse/YARN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-308: --- Fix Version/s: (was: 2.0.3-alpha) 2.0.4-beta > Improve documentation about w

[jira] [Updated] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-160: --- Fix Version/s: (was: 2.0.3-alpha) 2.0.4-beta > nodemanagers should obtain cp

[jira] [Updated] (YARN-153) PaaS on YARN: an YARN application to demonstrate that YARN can be used as a PaaS

[ https://issues.apache.org/jira/browse/YARN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-153: --- Fix Version/s: (was: 2.0.3-alpha) 2.0.4-beta > PaaS on YARN: an YARN applica

[jira] [Updated] (YARN-397) RM Scheduler api enhancements

[ https://issues.apache.org/jira/browse/YARN-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-397: --- Summary: RM Scheduler api enhancements (was: RM api enhancements) > RM Scheduler api enhancements

[jira] [Created] (YARN-398) Allow white-list and black-list of resources

Arun C Murthy created YARN-398: -- Summary: Allow white-list and black-list of resources Key: YARN-398 URL: https://issues.apache.org/jira/browse/YARN-398 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-394) RM should be able to return requests that it cannot fulfill

[ https://issues.apache.org/jira/browse/YARN-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-394: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-397 > RM should be able to return req

[jira] [Updated] (YARN-393) In RM * is overloaded for locality as well as resource demand

[ https://issues.apache.org/jira/browse/YARN-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-393: --- Issue Type: Sub-task (was: Bug) Parent: YARN-397 > In RM * is overloaded for locality as w

[jira] [Updated] (YARN-394) RM should be able to return requests that it cannot fulfill

[ https://issues.apache.org/jira/browse/YARN-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-394: --- Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-386) > RM should be able to

[jira] [Updated] (YARN-395) RM should have a way to disable scheduling to a set of nodes

[ https://issues.apache.org/jira/browse/YARN-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-395: --- Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-386) > RM should have a way

[jira] [Commented] (YARN-386) [Umbrella] YARN API cleanup

[ https://issues.apache.org/jira/browse/YARN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576401#comment-13576401 ] Arun C Murthy commented on YARN-386: Let's keep limited to API cleanup, and use YARN-397

[jira] [Updated] (YARN-393) In RM * is overloaded for locality as well as resource demand

[ https://issues.apache.org/jira/browse/YARN-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-393: --- Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) > In RM * is overloaded for lo

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-392: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-397 > Make it possible to schedule to

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-392: --- Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-386) > Make it possible to

[jira] [Created] (YARN-397) RM api enhancements

Arun C Murthy created YARN-397: -- Summary: RM api enhancements Key: YARN-397 URL: https://issues.apache.org/jira/browse/YARN-397 Project: Hadoop YARN Issue Type: Bug Reporter: Arun C

[jira] [Updated] (YARN-386) [Umbrella] YARN API cleanup

[ https://issues.apache.org/jira/browse/YARN-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-386: --- Summary: [Umbrella] YARN API cleanup (was: [Umbrella] YARN API cleanup and improvements) > [Umbre

[jira] [Assigned] (YARN-395) RM should have a way to disable scheduling to a set of nodes

[ https://issues.apache.org/jira/browse/YARN-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-395: -- Assignee: Arun C Murthy > RM should have a way to disable scheduling to a set of nodes >

[jira] [Assigned] (YARN-396) Rationalize AllocateResponse in RM scheduler API

[ https://issues.apache.org/jira/browse/YARN-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-396: -- Assignee: Arun C Murthy > Rationalize AllocateResponse in RM scheduler API >

[jira] [Assigned] (YARN-393) In RM * is overloaded for locality as well as resource demand

[ https://issues.apache.org/jira/browse/YARN-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-393: -- Assignee: Arun C Murthy > In RM * is overloaded for locality as well as resource demand > ---

[jira] [Commented] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574756#comment-13574756 ] Arun C Murthy commented on YARN-389: The way to fix this to cap yarn.scheduler.maximum-a

[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-tabpanel&focusedCommentId=13572484#comment-13572484 ] Arun C Murthy commented on YARN-3: -- Merged to branch-2. > Add support for CP

[jira] [Updated] (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:all-tabpanel ] Arun C Murthy updated YARN-3: - Fix Version/s: (was: 3.0.0) 2.0.3-alpha > Add support for CPU isolation/monitoring

[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-tabpanel&focusedCommentId=13572476#comment-13572476 ] Arun C Murthy commented on YARN-3: -- I didn't realize that this never made it to branch-2, I'l

[jira] [Assigned] (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 ] Arun C Murthy reassigned YARN-382: -- Assignee: Zhijie Shen Thomas - In the aftermath of YARN-370 I've been thinking that the right so

[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-tabpanel&focusedCommentId=13571937#comment-13571937 ] Arun C Murthy commented on YARN-370: Thanks Thomas! Zhijie, to be safe I think we shoul

[jira] [Commented] (YARN-371) Resource-centric compression in AM-RM protocol limits scheduling

[ https://issues.apache.org/jira/browse/YARN-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571763#comment-13571763 ] Arun C Murthy commented on YARN-371: bq. 100,000 tasks at 150 bytes each (name of 3 node

[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-tabpanel&focusedCommentId=13571545#comment-13571545 ] Arun C Murthy commented on YARN-370: Maybe something like this? {code} diff --git hado

[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-tabpanel&focusedCommentId=13571528#comment-13571528 ] Arun C Murthy commented on YARN-370: I agree, independently verified CS seems to work fi

[jira] [Commented] (YARN-371) Resource-centric compression in AM-RM protocol limits scheduling

[ https://issues.apache.org/jira/browse/YARN-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570633#comment-13570633 ] Arun C Murthy commented on YARN-371: Jira isn't a particularly good medium to have a dis

[jira] [Commented] (YARN-375) FIFO scheduler may crash due to bugg app

[ https://issues.apache.org/jira/browse/YARN-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570545#comment-13570545 ] Arun C Murthy commented on YARN-375: I believe this doesn't happen at all since there is

[jira] [Assigned] (YARN-375) FIFO scheduler may crash due to bugg app

[ https://issues.apache.org/jira/browse/YARN-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-375: -- Assignee: Arun C Murthy > FIFO scheduler may crash due to bugg app > --

[jira] [Commented] (YARN-371) Consolidate resource requests in AM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570325#comment-13570325 ] Arun C Murthy commented on YARN-371: Sandy - please don't let this side discussion distr

[jira] [Commented] (YARN-371) Consolidate resource requests in AM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570314#comment-13570314 ] Arun C Murthy commented on YARN-371: {quote} Looks like there's a misunderstanding here

[jira] [Comment Edited] (YARN-371) Consolidate resource requests in AM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569277#comment-13569277 ] Arun C Murthy edited comment on YARN-371 at 2/1/13 11:56 PM: - {q

[jira] [Commented] (YARN-371) Consolidate resource requests in AM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569277#comment-13569277 ] Arun C Murthy commented on YARN-371: {quote} I would propose the tweak of allowing a sin

[jira] [Updated] (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:all-tabpanel ] Arun C Murthy updated YARN-370: --- Priority: Blocker (was: Critical) > CapacityScheduler app submission fails when min alloc size not

[jira] [Updated] (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:all-tabpanel ] Arun C Murthy updated YARN-370: --- Target Version/s: 2.0.3-alpha (was: 3.0.0, 2.0.3-alpha) > CapacityScheduler app submission fails w

[jira] [Updated] (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:all-tabpanel ] Arun C Murthy updated YARN-370: --- Affects Version/s: (was: 3.0.0) > CapacityScheduler app submission fails when min alloc size no

[jira] [Updated] (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:all-tabpanel ] Arun C Murthy updated YARN-370: --- Assignee: Zhijie Shen > CapacityScheduler app submission fails when min alloc size not multiple of

[jira] [Commented] (YARN-294) Fixup YARN-2 naming and other nits in comments

[ https://issues.apache.org/jira/browse/YARN-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568278#comment-13568278 ] Arun C Murthy commented on YARN-294: bq. modifies DominantResourceCalculator#getResource

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567122#comment-13567122 ] Arun C Murthy commented on YARN-366: +1, good idea. > Add a tracing asy

[jira] [Commented] (YARN-343) Capacity Scheduler maximum-capacity value -1 is invalid

[ https://issues.apache.org/jira/browse/YARN-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566721#comment-13566721 ] Arun C Murthy commented on YARN-343: Sorry, one thing I failed to notice... We really s

[jira] [Commented] (YARN-333) On app submission, have RM ask scheduler for queue name

[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561071#comment-13561071 ] Arun C Murthy commented on YARN-333: How does this work in hadoop-1? There are no featur

[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-tabpanel&focusedCommentId=13560938#comment-13560938 ] Arun C Murthy commented on YARN-355: Daryn - do you remember the JT jira?

[jira] [Commented] (YARN-231) Add persistent store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559759#comment-13559759 ] Arun C Murthy commented on YARN-231: +1, thanks Bikas! > Add persistent

[jira] [Commented] (YARN-343) Capacity Scheduler maximum-capacity value -1 is invalid

[ https://issues.apache.org/jira/browse/YARN-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557718#comment-13557718 ] Arun C Murthy commented on YARN-343: Agreed, looks like a bug. > Capaci

[jira] [Updated] (YARN-343) Capacity Scheduler maximum-capacity value -1 is invalid

[ https://issues.apache.org/jira/browse/YARN-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-343: --- Assignee: Xuan Gong > Capacity Scheduler maximum-capacity value -1 is invalid > ---

[jira] [Resolved] (YARN-344) Node update causes NPE in the fair scheduler when requests of rack is null

[ https://issues.apache.org/jira/browse/YARN-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved YARN-344. Resolution: Duplicate Resolving as duplicate of YARN-335. Please re-open if you still see it.

[jira] [Commented] (YARN-340) Rename DefaultResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553278#comment-13553278 ] Arun C Murthy commented on YARN-340: Eli - I was specifically asked to not call it Memor

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548599#comment-13548599 ] Arun C Murthy commented on YARN-325: Thanks [~tgraves]! > RM CapacitySc

[jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-325: --- Attachment: YARN-325.patch Added unit-tests. > RM CapacityScheduler can deadlock when

[jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-325: --- Attachment: YARN-325.patch Illustrative patch, need to fix unit-tests yet. > RM Capaci

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547677#comment-13547677 ] Arun C Murthy commented on YARN-325: Ok, the fix is to bubble the 'non-requirement' of t

[jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-325: --- Priority: Blocker (was: Critical) > RM CapacityScheduler can deadlock when getQueueInfo() is calle

[jira] [Assigned] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-325: -- Assignee: Arun C Murthy > RM CapacityScheduler can deadlock when getQueueInfo() is called and

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547673#comment-13547673 ] Arun C Murthy commented on YARN-325: [~jlowe] This seems limited to a corner case (not t

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546824#comment-13546824 ] Arun C Murthy commented on YARN-2: -- Fixed TestRMWebServicesCapacitySched (had to fix the test

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Created] (YARN-322) Add cpu information to queue metrics

Arun C Murthy created YARN-322: -- Summary: Add cpu information to queue metrics Key: YARN-322 URL: https://issues.apache.org/jira/browse/YARN-322 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch Added default values to *-default.xml for documentation. > Enhance

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540746#comment-13540746 ] Arun C Murthy commented on YARN-2: -- [~sandyr] See the discussion between Bikas & I w.r.t defi

<    1   2   3   4   5   6   7   >