[jira] [Commented] (YARN-2297) Preemption can hang in corner case by not allowing any task container to proceed.

[ https://issues.apache.org/jira/browse/YARN-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14063229#comment-14063229 ] Sunil G commented on YARN-2297: --- Hi [~wangda] Couple of points: 1. {code} if (toBePreempt

[jira] [Commented] (YARN-2285) Preemption can cause capacity scheduler to show 5,000% queue capacity.

[ https://issues.apache.org/jira/browse/YARN-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14063710#comment-14063710 ] Sunil G commented on YARN-2285: --- I also got 106% in root queue with user-factor configured as

[jira] [Commented] (YARN-2293) Scoring for NMs to identify a better candidate to launch AMs

[ https://issues.apache.org/jira/browse/YARN-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14063772#comment-14063772 ] Sunil G commented on YARN-2293: --- Thank you [~jlowe] for update. Yes, it generically coming

[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=14063783#comment-14063783 ] Sunil G commented on YARN-796: -- 2. Regarding reservations, how about introducing node-label

[jira] [Commented] (YARN-2305) When a container is in reserved state then total cluster memory is displayed wrongly.

[ https://issues.apache.org/jira/browse/YARN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064736#comment-14064736 ] Sunil G commented on YARN-2305: --- No. Its a capacity scheduler. I could collect logs from

[jira] [Commented] (YARN-2305) When a container is in reserved state then total cluster memory is displayed wrongly.

[ https://issues.apache.org/jira/browse/YARN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064737#comment-14064737 ] Sunil G commented on YARN-2305: --- Hi [~zhiguohong], Could I take over the issue.. When a

[jira] [Assigned] (YARN-2305) When a container is in reserved state then total cluster memory is displayed wrongly.

[ https://issues.apache.org/jira/browse/YARN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-2305: - Assignee: Sunil G (was: Hong Zhiguo) When a container is in reserved state then total cluster memory is

[jira] [Commented] (YARN-2307) Capacity scheduler user only ADMINISTER_QUEUE also can submit app

[ https://issues.apache.org/jira/browse/YARN-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064760#comment-14064760 ] Sunil G commented on YARN-2307: --- By default, SUBMIT_APPLICATIONS at root queue level can take

[jira] [Commented] (YARN-2305) When a container is in reserved state then total cluster memory is displayed wrongly.

[ https://issues.apache.org/jira/browse/YARN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065238#comment-14065238 ] Sunil G commented on YARN-2305: --- 1. Yes [~leftnoteasy], GUI display of 106% is similar to

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065363#comment-14065363 ] Sunil G commented on YARN-2308: --- During *RMAppRecoveredTransition* in RMAppImpl, may be we

[jira] [Commented] (YARN-2297) Preemption can prevent progress in small queues

[ https://issues.apache.org/jira/browse/YARN-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14066615#comment-14066615 ] Sunil G commented on YARN-2297: --- Hi [~gp.leftnoteasy] bq. 1 Use (guaranteed - used) I feel

[jira] [Commented] (YARN-2301) Improve yarn container command

[ https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071705#comment-14071705 ] Sunil G commented on YARN-2301: --- This will be really useful enhancement. I have a concern

[jira] [Commented] (YARN-2301) Improve yarn container command

[ https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071838#comment-14071838 ] Sunil G commented on YARN-2301: --- bq.we can update the usage block to let users how to use the

[jira] [Created] (YARN-2356) yarn status command for non-existent application/application attempt/container is too verbose

Sunil G created YARN-2356: - Summary: yarn status command for non-existent application/application attempt/container is too verbose Key: YARN-2356 URL: https://issues.apache.org/jira/browse/YARN-2356

[jira] [Updated] (YARN-2356) yarn status command for non-existent application/application attempt/container is too verbose

[ https://issues.apache.org/jira/browse/YARN-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2356: -- Attachment: Yarn-2356.1.patch Fixed to handle ApplicationNotFoundException,

[jira] [Commented] (YARN-2362) Capacity Scheduler: apps with requests that exceed current capacity can starve pending apps

[ https://issues.apache.org/jira/browse/YARN-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075925#comment-14075925 ] Sunil G commented on YARN-2362: --- Possible duplicate of YARN-1631 Capacity Scheduler: apps

[jira] [Assigned] (YARN-1631) Container allocation issue in Leafqueue assignContainers()

[ https://issues.apache.org/jira/browse/YARN-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-1631: - Assignee: Sunil G Container allocation issue in Leafqueue assignContainers()

[jira] [Commented] (YARN-2283) RM failed to release the AM container

[ https://issues.apache.org/jira/browse/YARN-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079234#comment-14079234 ] Sunil G commented on YARN-2283: --- I tried to reproduce this and I found AM memory is

[jira] [Commented] (YARN-2283) RM failed to release the AM container

[ https://issues.apache.org/jira/browse/YARN-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080804#comment-14080804 ] Sunil G commented on YARN-2283: --- Seems to be duplicate to MAPREDUCE-5888 [~jlowe] cud u pls

[jira] [Commented] (YARN-2301) Improve yarn container command

[ https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14083940#comment-14083940 ] Sunil G commented on YARN-2301: --- I didn't get ur mail. But this response wud suffice.

[jira] [Commented] (YARN-2301) Improve yarn container command

[ https://issues.apache.org/jira/browse/YARN-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14083943#comment-14083943 ] Sunil G commented on YARN-2301: --- Sorry. Please discard my earlier comment. Improve yarn

[jira] [Commented] (YARN-2385) Adding support for listing all applications in a queue

[ https://issues.apache.org/jira/browse/YARN-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095718#comment-14095718 ] Sunil G commented on YARN-2385: --- I am not sure whether we need to check about completed apps

[jira] [Commented] (YARN-2390) Investigating whehther generic history service needs to support application-acls

[ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095725#comment-14095725 ] Sunil G commented on YARN-2390: --- For getting application report, container report etc,

[jira] [Commented] (YARN-2136) RMStateStore can explicitly handle store/update events when fenced

[ https://issues.apache.org/jira/browse/YARN-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095734#comment-14095734 ] Sunil G commented on YARN-2136: --- bq.we will wait till all these events have been processed

[jira] [Commented] (YARN-2390) Investigating whehther generic history service needs to support queue-acls

[ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097280#comment-14097280 ] Sunil G commented on YARN-2390: --- Yes. I understood your idea, but completed apps can be there

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097298#comment-14097298 ] Sunil G commented on YARN-2056: --- +1 This make sense. I have a doubt though.

[jira] [Commented] (YARN-2136) RMStateStore can explicitly handle store/update events when fenced

[ https://issues.apache.org/jira/browse/YARN-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097341#comment-14097341 ] Sunil G commented on YARN-2136: --- Yes. I also feel we need to flip the order for

[jira] [Commented] (YARN-2390) Investigating whehther generic history service needs to support queue-acls

[ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100724#comment-14100724 ] Sunil G commented on YARN-2390: --- Hi [~zjshen] bq. is the right fix to be correcting the ACLs

[jira] [Commented] (YARN-2310) Revisit the APIs in RM web services where user information can make difference

[ https://issues.apache.org/jira/browse/YARN-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100874#comment-14100874 ] Sunil G commented on YARN-2310: --- YARN-1867 has added queue ACL checks, and hasAccess is

[jira] [Assigned] (YARN-2390) Investigating whehther generic history service needs to support queue-acls

[ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-2390: - Assignee: Sunil G Investigating whehther generic history service needs to support queue-acls

[jira] [Commented] (YARN-2390) Investigating whehther generic history service needs to support queue-acls

[ https://issues.apache.org/jira/browse/YARN-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100949#comment-14100949 ] Sunil G commented on YARN-2390: --- Thank you [~zjshen] I have checked

[jira] [Commented] (YARN-2310) Revisit the APIs in RM web services where user information can make difference

[ https://issues.apache.org/jira/browse/YARN-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100963#comment-14100963 ] Sunil G commented on YARN-2310: --- Yes. getAppAttempts and getAppState could also fall in to

[jira] [Commented] (YARN-2385) Adding support for listing all applications in a queue

[ https://issues.apache.org/jira/browse/YARN-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102451#comment-14102451 ] Sunil G commented on YARN-2385: --- I feel this JIRA itself can be updated to split the

[jira] [Commented] (YARN-2385) Consider splitting getAppsinQueue to getRunningAppsInQueue + getPendingAppsInQueue

[ https://issues.apache.org/jira/browse/YARN-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14107896#comment-14107896 ] Sunil G commented on YARN-2385: --- After checking code,

[jira] [Commented] (YARN-2385) Consider splitting getAppsinQueue to getRunningAppsInQueue + getPendingAppsInQueue

[ https://issues.apache.org/jira/browse/YARN-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110849#comment-14110849 ] Sunil G commented on YARN-2385: --- Yes [~subru], _moveAllApps_ is also using this api. bq. If

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137013#comment-14137013 ] Sunil G commented on YARN-2308: --- +1 for this approach. I also feel that returning application

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137564#comment-14137564 ] Sunil G commented on YARN-1963: --- HI [~maysamyabandeh], We are bringing up a design doc for

[jira] [Commented] (YARN-2498) [YARN-796] Respect labels in preemption policy of capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142513#comment-14142513 ] Sunil G commented on YARN-2498: --- Hi [~wangda] Great work Wangda. Very good design to solve

[jira] [Updated] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1963: -- Attachment: YARN Application Priorities Design.pdf Hi All I am uploading an initial draft for Application

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149696#comment-14149696 ] Sunil G commented on YARN-1963: --- Thank you [~maysamyabandeh] for providing us the use cases.

[jira] [Updated] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1963: -- Attachment: (was: YARN Application Priorities Design.pdf) Support priorities across applications within the

[jira] [Updated] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1963: -- Attachment: YARN Application Priorities Design.pdf Attached updated design doc capturing comments. Thank you.

[jira] [Commented] (YARN-2647) [YARN-796] Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161395#comment-14161395 ] Sunil G commented on YARN-2647: --- Hi [~gp.leftnoteasy], I would like to take this up. Thank

[jira] [Assigned] (YARN-2647) [YARN-796] Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-2647: - Assignee: Sunil G [YARN-796] Add yarn queue CLI to get queue info including labels of such queue

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170860#comment-14170860 ] Sunil G commented on YARN-2495: --- Hi All. I have a doubt here, 1. In distributed

[jira] [Updated] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1963: -- Attachment: (was: YARN Application Priorities Design.pdf) Support priorities across applications within the

[jira] [Updated] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1963: -- Attachment: YARN Application Priorities Design.pdf Updating document with added information about user/admin

[jira] [Created] (YARN-2691) User level API support for priority label

Sunil G created YARN-2691: - Summary: User level API support for priority label Key: YARN-2691 URL: https://issues.apache.org/jira/browse/YARN-2691 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-2693) Priority Label Manager in RM to manage priority labels

Sunil G created YARN-2693: - Summary: Priority Label Manager in RM to manage priority labels Key: YARN-2693 URL: https://issues.apache.org/jira/browse/YARN-2693 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage priority labels

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Description: Focus of this JIRA is to have a centralized service to handle priority labels. Support operations

[jira] [Commented] (YARN-2504) Support get/add/remove/change labels in RM admin CLI

[ https://issues.apache.org/jira/browse/YARN-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172717#comment-14172717 ] Sunil G commented on YARN-2504: --- One comment: How *response* is populated for

[jira] [Commented] (YARN-2504) Support get/add/remove/change labels in RM admin CLI

[ https://issues.apache.org/jira/browse/YARN-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173236#comment-14173236 ] Sunil G commented on YARN-2504: --- Hi [~gp.leftnoteasy] {code}

[jira] [Commented] (YARN-2702) TestResourceTrackerOnHA fails with NPE

[ https://issues.apache.org/jira/browse/YARN-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174980#comment-14174980 ] Sunil G commented on YARN-2702: --- This is a possible duplicate to YARN-2699

[jira] [Commented] (YARN-2691) User level API support for priority label

[ https://issues.apache.org/jira/browse/YARN-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177302#comment-14177302 ] Sunil G commented on YARN-2691: --- A quick nit: ApplicationPriority can be comparable. This

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181474#comment-14181474 ] Sunil G commented on YARN-2647: --- Thank you Wangda. Sure. I will use the QueueInfo itself.

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14181701#comment-14181701 ] Sunil G commented on YARN-2647: --- Thank you [~gp.leftnoteasy] Yes. This is more or like what

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919153#comment-13919153 ] Sunil G commented on YARN-1769: --- Hi Thomas CapacityScheduler: Improve reservations

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919154#comment-13919154 ] Sunil G commented on YARN-1769: --- Hi Thomas CapacityScheduler: Improve reservations

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919161#comment-13919161 ] Sunil G commented on YARN-1769: --- Hi Thomas In LeafQueue assignContainer call, reserve() call

[jira] [Commented] (YARN-257) NM should gracefully handle a full local disk

[ https://issues.apache.org/jira/browse/YARN-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919295#comment-13919295 ] Sunil G commented on YARN-257: -- May be NM can do some level of handling by itself in Disk Full

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920488#comment-13920488 ] Sunil G commented on YARN-1781: --- Few comments from my side: NM should allow users to

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920489#comment-13920489 ] Sunil G commented on YARN-1781: --- 1. Disk Size can come down when some tasks finishes and

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920735#comment-13920735 ] Sunil G commented on YARN-1781: --- Thank you for the reply. I have another point in addition to

[jira] [Created] (YARN-1799) Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

Sunil G created YARN-1799: - Summary: Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff Key: YARN-1799 URL: https://issues.apache.org/jira/browse/YARN-1799 Project: Hadoop YARN

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923563#comment-13923563 ] Sunil G commented on YARN-1781: --- I have created a separate JIRA YARN-1799 as per the comment

[jira] [Commented] (YARN-1799) Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

[ https://issues.apache.org/jira/browse/YARN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923570#comment-13923570 ] Sunil G commented on YARN-1799: --- I would like to take up this JIRA. Enhance

[jira] [Commented] (YARN-1799) Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

[ https://issues.apache.org/jira/browse/YARN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925465#comment-13925465 ] Sunil G commented on YARN-1799: --- Yes Karthik. Existing logic is not considering the

[jira] [Updated] (YARN-1966) Capacity Scheduler acl_submit_applications in Leaf Queue finally considers root queue default always

[ https://issues.apache.org/jira/browse/YARN-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1966: -- Attachment: Yarn-1966.1.patch Here issue is happening because while submitting an application, hasAccess()

[jira] [Created] (YARN-1980) Possible NPE in KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy

Sunil G created YARN-1980: - Summary: Possible NPE in KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy Key: YARN-1980 URL: https://issues.apache.org/jira/browse/YARN-1980 Project: Hadoop

[jira] [Updated] (YARN-1980) Possible NPE in KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1980: -- Attachment: Yarn-1980.1.patch Possible NPE in KillAMPreemptionPolicy related to

[jira] [Commented] (YARN-1980) Possible NPE in KillAMPreemptionPolicy related to ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979662#comment-13979662 ] Sunil G commented on YARN-1980: --- The problem is because while setting the preemption message

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985160#comment-13985160 ] Sunil G commented on YARN-1963: --- We have done few analysis and implemented support for

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985318#comment-13985318 ] Sunil G commented on YARN-1963: --- Thank you Sandy for the review. As you have mentioned, I

[jira] [Created] (YARN-2002) Support for passing Job priority through Application Submission Context in Mapreduce Side

Sunil G created YARN-2002: - Summary: Support for passing Job priority through Application Submission Context in Mapreduce Side Key: YARN-2002 URL: https://issues.apache.org/jira/browse/YARN-2002 Project:

[jira] [Created] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

Sunil G created YARN-2003: - Summary: Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side] Key: YARN-2003 URL: https://issues.apache.org/jira/browse/YARN-2003

[jira] [Created] (YARN-2004) Job Priority scheduling support in Capacity scheduler

Sunil G created YARN-2004: - Summary: Job Priority scheduling support in Capacity scheduler Key: YARN-2004 URL: https://issues.apache.org/jira/browse/YARN-2004 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985340#comment-13985340 ] Sunil G commented on YARN-2003: --- ApplicationSubmissionContext already has an implementation

[jira] [Updated] (YARN-2002) Support for passing Job priority through Application Submission Context in Mapreduce Side

[ https://issues.apache.org/jira/browse/YARN-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2002: -- Attachment: Yarn-2002.1.patch Test cases are not added here, intended to cover as part of Yarn-2004 Support

[jira] [Commented] (YARN-2009) Priority support for preemption in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986679#comment-13986679 ] Sunil G commented on YARN-2009: --- As per YARN-1963, jobs can be submitted in a queue with

[jira] [Assigned] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-2003: - Assignee: Sunil G Support to process Job priority from Submission Context in

[jira] [Created] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

Sunil G created YARN-2022: - Summary: Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy Key: YARN-2022

[jira] [Updated] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2022: -- Description: Cluster Size = 16GB [2NM's] Queue A Capacity = 50% Queue B Capacity = 50% Consider there are 3

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994789#comment-13994789 ] Sunil G commented on YARN-2022: --- Hi [~curino] I have updated a patch as per the comments.

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994801#comment-13994801 ] Sunil G commented on YARN-1408: --- Please check the below scenario. After allocating a

[jira] [Assigned] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-1408: - Assignee: Sunil G Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997351#comment-13997351 ] Sunil G commented on YARN-2022: --- Thank you Carlo for the clarifications on am-priority and

[jira] [Updated] (YARN-2055) Preemption: Jobs are failing due to AMs are getting launched and killed multiple times

[ https://issues.apache.org/jira/browse/YARN-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2055: -- Summary: Preemption: Jobs are failing due to AMs are getting launched and killed multiple times (was:

[jira] [Commented] (YARN-2055) Preemption: Jobs are failing due to AMs are getting launched and killed multiple times

[ https://issues.apache.org/jira/browse/YARN-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997328#comment-13997328 ] Sunil G commented on YARN-2055: --- Hi Mayank, Is this issue same as YARN-2022 ? Preemption:

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995057#comment-13995057 ] Sunil G commented on YARN-2022: --- Thank you very much Carlo for the review. As per your

[jira] [Commented] (YARN-2055) Preemption: Jobs are failing due to AMs are getting launched and killed multiple times

[ https://issues.apache.org/jira/browse/YARN-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999724#comment-13999724 ] Sunil G commented on YARN-2055: --- Thank you Mayank for the clarification. I have a small doubt

[jira] [Assigned] (YARN-1799) Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

[ https://issues.apache.org/jira/browse/YARN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-1799: - Assignee: Sunil G Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

[jira] [Commented] (YARN-2074) Preemption of AM containers shouldn't count towards AM failures

[ https://issues.apache.org/jira/browse/YARN-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002800#comment-14002800 ] Sunil G commented on YARN-2074: --- Hi Vinod As per the description I understood that the AM

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006908#comment-14006908 ] Sunil G commented on YARN-1408: --- bq. we may change it to decrement the resource request only

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008576#comment-14008576 ] Sunil G commented on YARN-1408: --- Yes. As I mentioned in earlier comment, it is better to add

[jira] [Updated] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2022: -- Attachment: YARN-2022-DesignDraft.docx Hi [~curino] I have attached a Design Draft document and I tried to

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017633#comment-14017633 ] Sunil G commented on YARN-2022: --- Thank your very much Carlo for the review. Yes, I understood

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019696#comment-14019696 ] Sunil G commented on YARN-1408: --- bq. If container killed/preempted before transferred to

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019708#comment-14019708 ] Sunil G commented on YARN-1408: --- *Sorry I misunderstood, please discard my earlier comment*.

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019783#comment-14019783 ] Sunil G commented on YARN-1408: --- Hi [~leftnoteasy] bq.I meant we need keep a complete

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019813#comment-14019813 ] Sunil G commented on YARN-1408: --- Thank you Wangda for the comment. bq.FairScheduler supports

  1   2   3   4   5   6   7   8   9   10   >