[jira] [Commented] (YARN-9656) Plugin to avoid scheduling jobs on node which are not in "schedulable" state, but are healthy otherwise.

[ https://issues.apache.org/jira/browse/YARN-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951393#comment-16951393 ] Mayank Bansal commented on YARN-9656: - [~wangda] We should not make full cluster unhea

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Attachment: YARN-4161.patch Attaching patch > Capacity Scheduler : Assign single or multiple contain

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Description: Capacity Scheduler right now schedules multiple containers per heart beat if there are

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Fix Version/s: (was: 2.1.0-beta) > Capacity Scheduler : Assign single or multiple containers per

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Description: Capacity > Capacity Scheduler : Assign single or multiple containers per heart beat >

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Labels: (was: BB2015-05-TBR) > Capacity Scheduler : Assign single or multiple containers per heart

[jira] [Updated] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

[ https://issues.apache.org/jira/browse/YARN-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-4161: Description: (was: This is different from (even if related to, and likely share code with) YARN-2

[jira] [Created] (YARN-4161) Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration

Mayank Bansal created YARN-4161: --- Summary: Capacity Scheduler : Assign single or multiple containers per heart beat driven by configuration Key: YARN-4161 URL: https://issues.apache.org/jira/browse/YARN-4161

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-2.6-11.patch Uploading the 2.6 patch Thanks, Mayank > CS queue level preempti

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-9.patch > Capacity Scheduler preemption policy should only consider capacity wi

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279056#comment-14279056 ] Mayank Bansal commented on YARN-2933: - Thanks [~jianhe] and [~wangda] for the review b

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-8.patch > Capacity Scheduler preemption policy should only consider capacity wi

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277328#comment-14277328 ] Mayank Bansal commented on YARN-2933: - Thanks [~wangda] for review. bq. 1) Proportiona

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275989#comment-14275989 ] Mayank Bansal commented on YARN-2933: - This test failure is not due to this patch. Tha

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-7.patch Thanks [~wangda][~jianhe]and [~sunilg] for reviews Updated the patch

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-6.patch Attaching patch Thanks, Mayank > Capacity Scheduler preemption policy

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269784#comment-14269784 ] Mayank Bansal commented on YARN-2933: - Thanks [~wangda] and Sunil for review. bq. In a

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267962#comment-14267962 ] Mayank Bansal commented on YARN-2933: - Thanks [~wangda] for review. 1. Fixed, I should

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-5.patch Updating patch. Thanks, Mayank > Capacity Scheduler preemption policy

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-4.patch Thanks [~wangda] for review. I updated the patch based on the comments

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257717#comment-14257717 ] Mayank Bansal commented on YARN-2933: - These findbugs is not due to this patch, Thanks

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-3.patch Fixing javadoc warnings Thanks, Mayank > Capacity Scheduler preemptio

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-2.patch Thanks [~wangda] for the review. Make sense. Updating the patch. Thank

[jira] [Commented] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252629#comment-14252629 ] Mayank Bansal commented on YARN-2933: - These find bug and test failure is not due to th

[jira] [Updated] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2933: Attachment: YARN-2933-1.patch Attaching patch for avoiding preemption for labeled containers. Thanks

[jira] [Assigned] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily

[ https://issues.apache.org/jira/browse/YARN-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-2933: --- Assignee: Mayank Bansal (was: Wangda Tan) Taking it over > Capacity Scheduler preemption pol

[jira] [Commented] (YARN-2698) Move getClusterNodeLabels and getNodeToLabels to YARN CLI instead of RMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179379#comment-14179379 ] Mayank Bansal commented on YARN-2698: - taking it over Thanks, Mayank > Move getCluste

[jira] [Assigned] (YARN-2698) Move getClusterNodeLabels and getNodeToLabels to YARN CLI instead of RMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-2698: --- Assignee: Mayank Bansal (was: Wangda Tan) > Move getClusterNodeLabels and getNodeToLabels to

[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-tabpanel&focusedCommentId=14179377#comment-14179377 ] Mayank Bansal commented on YARN-2647: - HI [~sunilg] , Are u still working on this ? Ca

[jira] [Created] (YARN-2670) Adding feedback capability to capacity scheduler from external systems

Mayank Bansal created YARN-2670: --- Summary: Adding feedback capability to capacity scheduler from external systems Key: YARN-2670 URL: https://issues.apache.org/jira/browse/YARN-2670 Project: Hadoop YARN

[jira] [Commented] (YARN-2320) Removing old application history store after we store the history data to timeline store

[ https://issues.apache.org/jira/browse/YARN-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165795#comment-14165795 ] Mayank Bansal commented on YARN-2320: - Thanks [~zjshen] for the patch overall looks ok

[jira] [Commented] (YARN-2598) GHS should show N/A instead of null for the inaccessible information

[ https://issues.apache.org/jira/browse/YARN-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165715#comment-14165715 ] Mayank Bansal commented on YARN-2598: - Committed to branch 2, 2,6 and trunk Thanks [~zj

[jira] [Commented] (YARN-2320) Removing old application history store after we store the history data to timeline store

[ https://issues.apache.org/jira/browse/YARN-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152559#comment-14152559 ] Mayank Bansal commented on YARN-2320: - I think overal looks ok however Have to run. s

[jira] [Commented] (YARN-2598) GHS should show N/A instead of null for the inaccessible information

[ https://issues.apache.org/jira/browse/YARN-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152534#comment-14152534 ] Mayank Bansal commented on YARN-2598: - +1 LGTM. Will run tests and if succeeds will com

[jira] [Updated] (YARN-2459) RM crashes if App gets rejected for any reason and HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2459: Attachment: YARN-2459-2.patch Attaching patch after oflline discussion with [~jianhe] Thanks, Mayan

[jira] [Updated] (YARN-2459) RM crashes if App gets rejected for any reason and HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2459: Description: If RM HA is enabled and used Zookeeper store for RM State Store. If for any reason Any

[jira] [Updated] (YARN-2459) RM crashes if App gets rejected for any reason and HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2459: Attachment: YARN-2459-1.patch Updating patch , Adding app to state store in App reject event to make

[jira] [Created] (YARN-2459) RM crashes if App gets rejected for any reason and HA is enabled

Mayank Bansal created YARN-2459: --- Summary: RM crashes if App gets rejected for any reason and HA is enabled Key: YARN-2459 URL: https://issues.apache.org/jira/browse/YARN-2459 Project: Hadoop YARN

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-10.patch Fixing small bug. Thanks, Mayank > CS queue level preemption

[jira] [Updated] (YARN-2032) Implement a scalable, available TimelineStore using HBase

[ https://issues.apache.org/jira/browse/YARN-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2032: Attachment: YARN-2032-branch2-2.patch Attching update patch for branch 2 Thanks, Mayank > Implemen

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-9.patch Fixing findbug warning and adding one more test case for no user

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-8.patch > CS queue level preemption should respect user-limits > ---

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081193#comment-14081193 ] Mayank Bansal commented on YARN-2069: - Hi [~wangda] , Thanks for your review comments.

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074940#comment-14074940 ] Mayank Bansal commented on YARN-2069: - HI [~wangda] , Thanks for the review. Let me e

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-7.patch Updated patch Thanks, Mayank > CS queue level preemption shoul

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073727#comment-14073727 ] Mayank Bansal commented on YARN-2069: - Thanks [~vinodkv] for the review. I have change

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-6.patch > CS queue level preemption should respect user-limits > ---

[jira] [Updated] (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 ] Mayank Bansal updated YARN-1408: Fix Version/s: 2.6.0 2.5.0 > Preemption caused Invalid State Event: ACQUIRED at K

[jira] [Updated] (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 ] Mayank Bansal updated YARN-1408: Attachment: YARN-1408-branch-2.5-1.patch rebasing against branch 2.5 > Preemption caused Invalid S

[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-tabpanel&focusedCommentId=14062879#comment-14062879 ] Mayank Bansal commented on YARN-1408: - Committed to trunk, branch 2 and branch-2.5. br

[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-tabpanel&focusedCommentId=14062698#comment-14062698 ] Mayank Bansal commented on YARN-1408: - +1 Committing Thanks [~sunilg] for the patch. T

[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-tabpanel&focusedCommentId=14061320#comment-14061320 ] Mayank Bansal commented on YARN-1408: - [~sunilg], Can you check these test failures? T

[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-tabpanel&focusedCommentId=14060929#comment-14060929 ] Mayank Bansal commented on YARN-1408: - At [~jianhe] 's point . I think its good to che

[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-tabpanel&focusedCommentId=14059104#comment-14059104 ] Mayank Bansal commented on YARN-1408: - Thanks [~sunilg] for the patch. Patch Looks good

[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-tabpanel&focusedCommentId=14057200#comment-14057200 ] Mayank Bansal commented on YARN-1408: - Thanks [~sunilg] for the patch. Patch looks goo

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057170#comment-14057170 ] Mayank Bansal commented on YARN-2069: - I just verified, rebased the patch and compiled

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-5.patch Thanks [~wangda] and [~sunilg] for the review. I have update al

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-4.patch > CS queue level preemption should respect user-limits > ---

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055598#comment-14055598 ] Mayank Bansal commented on YARN-2069: - Hi [~wangda], Good point , I missed it. I have

[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-tabpanel&focusedCommentId=14054648#comment-14054648 ] Mayank Bansal commented on YARN-2022: - Merged to Branch 2.5 Thanks, Mayank > Preempti

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054339#comment-14054339 ] Mayank Bansal commented on YARN-2069: - [~wangda] bq. Assume a queue has 10 apps, each

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Description: This is different from (even if related to, and likely share code with) YARN-2113. YA

[jira] [Updated] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2113: Description: Preemption today only works across queues and moves around resources across queues per

[jira] [Updated] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Summary: CS queue level preemption should respect user-limits (was: Add cross-user preemption withi

[jira] [Updated] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2113: Summary: Add cross-user preemption within CapacityScheduler's leaf-queue (was: CS queue level preem

[jira] [Commented] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053959#comment-14053959 ] Mayank Bansal commented on YARN-2069: - hi [~wangda], Thanks for the review. I updated

[jira] [Updated] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-3.patch Rebasing and Updating the patch. Thanks, Mayank > Add cross-us

[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-tabpanel&focusedCommentId=14049529#comment-14049529 ] Mayank Bansal commented on YARN-2022: - + 1 committing Thanks [~sunilg] for the patch.

[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-tabpanel&focusedCommentId=14048308#comment-14048308 ] Mayank Bansal commented on YARN-2022: - Thanks [~sunilg] for the patch. {code} publ

[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-tabpanel&focusedCommentId=14045386#comment-14045386 ] Mayank Bansal commented on YARN-2022: - You are using getAbsoluteMaximumCapacity() in yo

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044218#comment-14044218 ] Mayank Bansal commented on YARN-2181: - If we are adding this information into Web UI th

[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-tabpanel&focusedCommentId=14044217#comment-14044217 ] Mayank Bansal commented on YARN-2022: - Hi [~sunilg] If we dont use getAbsoluteCapacity

[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-tabpanel&focusedCommentId=14042760#comment-14042760 ] Mayank Bansal commented on YARN-2022: - HI [~sunilg] Thanks for the patch. I have look

[jira] [Updated] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-2.patch Thanks for the review. I don't have any easy way now to seprate

[jira] [Updated] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-1.patch Attaching patch Thanks, Mayank > Add cross-user preemption wit

[jira] [Commented] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041617#comment-14041617 ] Mayank Bansal commented on YARN-2069: - Taking it over. Thanks, Mayank > Add cross-use

[jira] [Assigned] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-2069: --- Assignee: Mayank Bansal (was: Vinod Kumar Vavilapalli) > Add cross-user preemption within Cap

[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-tabpanel&focusedCommentId=14041435#comment-14041435 ] Mayank Bansal commented on YARN-2022: - Hi [~vinodkv] Is this ok with you if we commit t

[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-tabpanel&focusedCommentId=14032918#comment-14032918 ] Mayank Bansal commented on YARN-2022: - HI [~sunilg] Thanks for the patch. Overall lo

[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-tabpanel&focusedCommentId=14030143#comment-14030143 ] Mayank Bansal commented on YARN-2022: - Hi [~vinodkv] what you are saying make sense an

[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-tabpanel&focusedCommentId=14028174#comment-14028174 ] Mayank Bansal commented on YARN-2022: - hi [~sunilg] Thanks for the patch. There is s

[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-tabpanel&focusedCommentId=14026795#comment-14026795 ] Mayank Bansal commented on YARN-2022: - for user limits there is already a jira YARN-211

[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-tabpanel&focusedCommentId=14026789#comment-14026789 ] Mayank Bansal commented on YARN-2022: - Hi [~sunilg] Thanks for the update. We are in t

[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-tabpanel&focusedCommentId=14025581#comment-14025581 ] Mayank Bansal commented on YARN-2022: - Hi [~sunilg] and [~curino] Me and [~vinodkv] we

[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-tabpanel&focusedCommentId=14006735#comment-14006735 ] Mayank Bansal commented on YARN-2074: - +1 LGTM Thanks, Mayank > Preemption of AM cont

[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-tabpanel&focusedCommentId=14006548#comment-14006548 ] Mayank Bansal commented on YARN-1408: - I agree with [~jianhe] and [~devaraj.k] We shoul

[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-tabpanel&focusedCommentId=14006459#comment-14006459 ] Mayank Bansal commented on YARN-2074: - Thanks [~jianhe] for the patch. Overall looks go

[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-tabpanel&focusedCommentId=13998941#comment-13998941 ] Mayank Bansal commented on YARN-2055: - YARN-2022 is for avoiding killing AM however thi

[jira] [Updated] (YARN-2055) Preemtion: 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 ] Mayank Bansal updated YARN-2055: Description: If Queue A does not have enough capacity to run AM, then AM will borrow capacity from q

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

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2056: Description: We need to be able to disable preemption at individual queue level (was: If Queue A do

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

Mayank Bansal created YARN-2055: --- Summary: Preemtion: Jobs are failing due to AMs are getting launched and killed multiple times Key: YARN-2055 URL: https://issues.apache.org/jira/browse/YARN-2055 Proje

[jira] [Updated] (YARN-2055) Preemtion: 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 ] Mayank Bansal updated YARN-2055: Assignee: (was: Sunil G) > Preemtion: Jobs are failing due to AMs are getting launched and kille

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

Mayank Bansal created YARN-2056: --- Summary: Disable preemption at Queue level Key: YARN-2056 URL: https://issues.apache.org/jira/browse/YARN-2056 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-2032) Implement a scalable, available TimelineStore using HBase

[ https://issues.apache.org/jira/browse/YARN-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2032: Attachment: YARN-2032-branch-2-1.patch Updating patch for branch-2 Thanks, Mayank > Implement a sc

[jira] [Commented] (YARN-2032) Implement a scalable, available TimelineStore using HBase

[ https://issues.apache.org/jira/browse/YARN-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993000#comment-13993000 ] Mayank Bansal commented on YARN-2032: - Taking it over, As I am already working on it T

[jira] [Assigned] (YARN-2032) Implement a scalable, available TimelineStore using HBase

[ https://issues.apache.org/jira/browse/YARN-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-2032: --- Assignee: Mayank Bansal (was: Vinod Kumar Vavilapalli) > Implement a scalable, available Time

[jira] [Commented] (YARN-1962) Timeline server is enabled by default

[ https://issues.apache.org/jira/browse/YARN-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990643#comment-13990643 ] Mayank Bansal commented on YARN-1962: - Hi [~zjshen] Can you please take a look ? Than

[jira] [Updated] (YARN-304) RM Tracking Links for purged applications needs a long-term solution

[ https://issues.apache.org/jira/browse/YARN-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-304: --- Attachment: YARN-304-1.patch Attaching patch Thanks, Mayank > RM Tracking Links for purged applicatio

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946731#comment-13946731 ] Mayank Bansal commented on YARN-1809: - Thanks [~zjshen] for the patch bq. Yes, I think

[jira] [Assigned] (YARN-304) RM Tracking Links for purged applications needs a long-term solution

[ https://issues.apache.org/jira/browse/YARN-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-304: -- Assignee: Mayank Bansal (was: Zhijie Shen) > RM Tracking Links for purged applications needs a l

  1   2   3   4   5   >