[
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
> --
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
> ---
[
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
[
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
[
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
[
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
[
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
[
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
[
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?
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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 *
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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
[
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
[
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
>
[
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
>
[
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
> ---
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
> --
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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?
[
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
[
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
[
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
> ---
[
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.
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
>
[
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
[
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
>
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
[
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
>
[
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
>
[
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
[
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
>
[
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
401 - 500 of 655 matches
Mail list logo