[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

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

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342938#comment-14342938 ] Varun Vasudev commented on YARN-3080: - Can you post another example showing the process

[jira] [Commented] (YARN-3281) Add RMStateStore to StateMachine visualization list

[ https://issues.apache.org/jira/browse/YARN-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342952#comment-14342952 ] Chengbing Liu commented on YARN-3281: - The patch is script-only. The findbugs warnings

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342994#comment-14342994 ] Beckham007 commented on YARN-3080: -- We can use "yarn containerId" as docker "container nam

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342996#comment-14342996 ] Beckham007 commented on YARN-3080: -- We can use "yarn containerId" as docker "container nam

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342995#comment-14342995 ] Beckham007 commented on YARN-3080: -- We can use "yarn containerId" as docker "container nam

[jira] [Commented] (YARN-3190) NM can't aggregate logs: token can't be found in cache

[ https://issues.apache.org/jira/browse/YARN-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342999#comment-14342999 ] Peng Zhang commented on YARN-3190: -- I met the same issue for spark streaming job running o

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343000#comment-14343000 ] Beckham007 commented on YARN-3080: -- [~vvasudev] the kill -9 couldn't work in this situati

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343006#comment-14343006 ] Varun Vasudev commented on YARN-3080: - [~beckham007] - we don't run "kill -9 $PID", we

[jira] [Updated] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3222: - Attachment: 0003-YARN-3222.patch > RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential >

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343036#comment-14343036 ] Rohith commented on YARN-3222: -- bq. are the test failures related ? Yes , Since totalCapabilit

[jira] [Resolved] (YARN-1853) Allow containers to be ran under real user even in insecure mode

[ https://issues.apache.org/jira/browse/YARN-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev resolved YARN-1853. Resolution: Duplicate > Allow containers to be ran under real user even in insecure mode > --

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

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

[jira] [Commented] (YARN-2190) Provide a Windows container executor that can limit memory and CPU

[ https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343220#comment-14343220 ] Ram Venkatesh commented on YARN-2190: - Apologies for the wrong reference in the comment

[jira] [Commented] (YARN-3116) [Aggregator wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343272#comment-14343272 ] Junping Du commented on YARN-3116: -- I think we can consider to add an optional field in Co

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Attachment: (was: 0006-YARN-2693.patch) > Priority Label Manager in RM to manage application priority based o

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Attachment: 0006-YARN-2693.patch Uploading with minor corrections. findbugs warnings seems unrelated > Priority

[jira] [Updated] (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 updated YARN-2003: -- Attachment: 0003-YARN-2003.patch Rebasing against YARN-2693 > Support to process Job priority from Submission Co

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Attachment: (was: 0006-YARN-2693.patch) > Priority Label Manager in RM to manage application priority based o

[jira] [Updated] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

[ https://issues.apache.org/jira/browse/YARN-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2693: -- Attachment: 0006-YARN-2693.patch > Priority Label Manager in RM to manage application priority based on > config

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

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2004: -- Attachment: 0003-YARN-2004.patch Updating patch with minor variations > Priority scheduling support in Capacity

[jira] [Updated] (YARN-2863) ResourceManager will shutdown when job's queuename is empty

[ https://issues.apache.org/jira/browse/YARN-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-2863: --- Fix Version/s: (was: 3.0.0) > ResourceManager will shutdown when job's queuename is empty >

[jira] [Updated] (YARN-3064) TestRMRestart/TestContainerResourceUsage/TestNodeManagerResync failure with allocation timeout

[ https://issues.apache.org/jira/browse/YARN-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3064: --- Fix Version/s: (was: 2.7.0) > TestRMRestart/TestContainerResourceUsage/TestNodeManagerResyn

[jira] [Updated] (YARN-3064) TestRMRestart/TestContainerResourceUsage/TestNodeManagerResync failure with allocation timeout

[ https://issues.apache.org/jira/browse/YARN-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-3064: --- Fix Version/s: (was: 3.0.0) 2.7.0 > TestRMRestart/TestContainerResourceU

[jira] [Commented] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343403#comment-14343403 ] Abin Shahab commented on YARN-3080: --- [~vvasudev], Thanks again for looking into this. I'

[jira] [Commented] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

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

[jira] [Commented] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343429#comment-14343429 ] Zhijie Shen commented on YARN-3210: --- Thanks for the patch. Two quick comments: 1. Can we

[jira] [Commented] (YARN-2693) Priority Label Manager in RM to manage application priority based on configuration

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

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343490#comment-14343490 ] Wangda Tan commented on YARN-3265: -- Findbugs warnings are not related to this change. > C

[jira] [Updated] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3272: -- Attachment: YARN-3272.3.patch > Surface container locality info > > >

[jira] [Commented] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343593#comment-14343593 ] Vinod Kumar Vavilapalli commented on YARN-3210: --- The REST server should be in

[jira] [Updated] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-2962: --- Attachment: YARN-2962.01.patch > ZKRMStateStore: Limit the number of znodes under a znode > ---

[jira] [Updated] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-2962: --- Attachment: (was: YARN-2962.01.patch) > ZKRMStateStore: Limit the number of znodes under a znode >

[jira] [Updated] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-2962: --- Attachment: YARN-2962.01.patch > ZKRMStateStore: Limit the number of znodes under a znode > ---

[jira] [Commented] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343625#comment-14343625 ] Jian He commented on YARN-3272: --- fixed the test failures. > Surface container locality info

[jira] [Commented] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343653#comment-14343653 ] Karthik Kambatla commented on YARN-2868: Sorry for coming in late. Few comments on

[jira] [Created] (YARN-3283) Scheduler MinimumAllocation is not refreshable

Vinod Kumar Vavilapalli created YARN-3283: - Summary: Scheduler MinimumAllocation is not refreshable Key: YARN-3283 URL: https://issues.apache.org/jira/browse/YARN-3283 Project: Hadoop YARN

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343698#comment-14343698 ] Vinod Kumar Vavilapalli commented on YARN-3265: --- LeafQueue.minimumAllocation

[jira] [Commented] (YARN-3272) Surface container locality info

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

[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=14343718#comment-14343718 ] Vinod Kumar Vavilapalli commented on YARN-2069: --- In the above example, there

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Attachment: YARN-3265.7.patch Vinod's suggestion makes sense to me, remove the volatile/findbugs-exclude an

[jira] [Updated] (YARN-2828) Enable auto refresh of web pages (using http parameter)

[ https://issues.apache.org/jira/browse/YARN-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay Bhat updated YARN-2828: - Attachment: YARN-2828.002.patch > Enable auto refresh of web pages (using http parameter) > ---

[jira] [Commented] (YARN-2828) Enable auto refresh of web pages (using http parameter)

[ https://issues.apache.org/jira/browse/YARN-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343737#comment-14343737 ] Vijay Bhat commented on YARN-2828: -- [~aw], thanks for the review. I wasn't able to find an

[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=14343739#comment-14343739 ] Hadoop QA commented on YARN-2069: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

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

[jira] [Commented] (YARN-2828) Enable auto refresh of web pages (using http parameter)

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

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343774#comment-14343774 ] Jason Lowe commented on YARN-3131: -- +1 lgtm. Will commit this tomorrow if there are no ob

[jira] [Updated] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3210: Attachment: YARN-3210-030215.patch Thanks [~zjshen] and [~vinodkv] for the review! I've attached a new patch accordi

[jira] [Commented] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343788#comment-14343788 ] Wangda Tan commented on YARN-3272: -- Patch LGTM overall, but could you take a look at findb

[jira] [Commented] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343794#comment-14343794 ] Li Lu commented on YARN-3210: - The patch would not apply to normal Jenkins run since Jenkins is

[jira] [Commented] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343801#comment-14343801 ] Zhijie Shen commented on YARN-3210: --- Thanks Li! Some additional comments 1. Can we renam

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343802#comment-14343802 ] Vinod Kumar Vavilapalli commented on YARN-3265: --- Looks good, +1. Will commit

[jira] [Created] (YARN-3284) Expose ApplicationPreemptionMetrics and ApplicationAttemptPreemptionMetrics through YARN command

Xuan Gong created YARN-3284: --- Summary: Expose ApplicationPreemptionMetrics and ApplicationAttemptPreemptionMetrics through YARN command Key: YARN-3284 URL: https://issues.apache.org/jira/browse/YARN-3284 Pr

[jira] [Updated] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3272: -- Attachment: YARN-3272.4.patch > Surface container locality info > > >

[jira] [Commented] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343832#comment-14343832 ] Zhijie Shen commented on YARN-3276: --- One nit: there's an existing TimelineUtils. > Fix N

[jira] [Commented] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343840#comment-14343840 ] Siqi Li commented on YARN-3231: --- Hi [~kasha], I have added two test cases for reducing User/Q

[jira] [Commented] (YARN-3284) Expose ApplicationPreemptionMetrics and ApplicationAttemptPreemptionMetrics through YARN command

[ https://issues.apache.org/jira/browse/YARN-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343844#comment-14343844 ] Vinod Kumar Vavilapalli commented on YARN-3284: --- Instead of making it preempt

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343846#comment-14343846 ] Jian He commented on YARN-3222: --- thanks for updating. I think we may not need to call sendNo

[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=14343867#comment-14343867 ] Wangda Tan commented on YARN-2069: -- This comment makes sense to me, maybe YARN-2113 should

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

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

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343896#comment-14343896 ] Jian He commented on YARN-3222: --- bq. I have handled this by sending RMNodeResourceUpdateEve

[jira] [Commented] (YARN-3281) Add RMStateStore to StateMachine visualization list

[ https://issues.apache.org/jira/browse/YARN-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343914#comment-14343914 ] Jian He commented on YARN-3281: --- looks good, checking in > Add RMStateStore to StateMachine

[jira] [Commented] (YARN-3281) Add RMStateStore to StateMachine visualization list

[ https://issues.apache.org/jira/browse/YARN-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343937#comment-14343937 ] Hudson commented on YARN-3281: -- FAILURE: Integrated in Hadoop-trunk-Commit #7237 (See [https:

[jira] [Updated] (YARN-3270) node label expression not getting set in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3270: - Assignee: Rohit Agarwal > node label expression not getting set in ApplicationSubmissionContext > -

[jira] [Updated] (YARN-3270) node label expression not getting set in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3270: - Target Version/s: 2.7.0 > node label expression not getting set in ApplicationSubmissionContext > -

[jira] [Commented] (YARN-3270) node label expression not getting set in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343939#comment-14343939 ] Wangda Tan commented on YARN-3270: -- [~ragarwal], thanks for reporting this. This was a pre

[jira] [Commented] (YARN-1453) [JDK8] Fix Javadoc errors caused by incorrect or illegal tags in doc comments

[ https://issues.apache.org/jira/browse/YARN-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343971#comment-14343971 ] Akira AJISAKA commented on YARN-1453: - Hi [~apurtell], how is this issue going? If you

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343979#comment-14343979 ] Jian He commented on YARN-3168: --- Is this planned for branch-2 ? otherwise documentation patc

[jira] [Commented] (YARN-3272) Surface container locality info

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

[jira] [Commented] (YARN-3187) Documentation of Capacity Scheduler Queue mapping based on user or group

[ https://issues.apache.org/jira/browse/YARN-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343985#comment-14343985 ] Jian He commented on YARN-3187: --- canceling the patch as its not applying any more after YARN-

[jira] [Commented] (YARN-3243) CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits.

[ https://issues.apache.org/jira/browse/YARN-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343995#comment-14343995 ] Wangda Tan commented on YARN-3243: -- How reservation continous looking works now: - For Par

[jira] [Commented] (YARN-2854) The document about timeline service and generic service needs to be updated

[ https://issues.apache.org/jira/browse/YARN-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343998#comment-14343998 ] Jian He commented on YARN-2854: --- unfortunately, YARN-3168 is in and this no longer applies on

[jira] [Updated] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3210: Attachment: YARN-3210-030215_1.patch Thanks [~zjshen]! I've updated my patch according to your review. Specifically,

[jira] [Updated] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Summary: Refactor and fix null casting in some map cast for TimelineEntity (old and new) (was: Fix NPE and

[jira] [Updated] (YARN-2828) Enable auto refresh of web pages (using http parameter)

[ https://issues.apache.org/jira/browse/YARN-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay Bhat updated YARN-2828: - Attachment: (was: YARN-2828.002.patch) > Enable auto refresh of web pages (using http parameter) >

[jira] [Updated] (YARN-2828) Enable auto refresh of web pages (using http parameter)

[ https://issues.apache.org/jira/browse/YARN-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay Bhat updated YARN-2828: - Attachment: YARN-2828.002.patch > Enable auto refresh of web pages (using http parameter) > ---

[jira] [Commented] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344075#comment-14344075 ] Junping Du commented on YARN-3276: -- Fix title to reflect what we discussion above. Thanks

[jira] [Updated] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3272: -- Attachment: YARN-3272.5.patch > Surface container locality info > > >

[jira] [Commented] (YARN-3210) [Source organization] Refactor timeline aggregator according to new code organization

[ https://issues.apache.org/jira/browse/YARN-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344096#comment-14344096 ] Zhijie Shen commented on YARN-3210: --- +1, LGTM > [Source organization] Refactor timeline

[jira] [Commented] (YARN-3284) Expose ApplicationPreemptionMetrics and ApplicationAttemptPreemptionMetrics through YARN command

[ https://issues.apache.org/jira/browse/YARN-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344101#comment-14344101 ] Xuan Gong commented on YARN-3284: - Yes, we should do that. Modify the title and Description

[jira] [Updated] (YARN-3284) Expose more ApplicationMetrics and ApplicationAttemptMetrics through YARN command

[ https://issues.apache.org/jira/browse/YARN-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3284: Summary: Expose more ApplicationMetrics and ApplicationAttemptMetrics through YARN command (was: Expose Appl

[jira] [Updated] (YARN-3284) Expose more ApplicationMetrics and ApplicationAttemptMetrics through YARN command

[ https://issues.apache.org/jira/browse/YARN-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3284: Description: Current, we have some extra metrics about the application and current attempt in RM Web UI. We

[jira] [Updated] (YARN-3204) Fix new findbug warnings in hadoop-yarn-server-resourcemanager(resourcemanager.scheduler.fair)

[ https://issues.apache.org/jira/browse/YARN-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3204: --- Attachment: YARN-3204-003.patch > Fix new findbug warnings in > hadoop-yarn-server-res

[jira] [Commented] (YARN-3204) Fix new findbug warnings in hadoop-yarn-server-resourcemanager(resourcemanager.scheduler.fair)

[ https://issues.apache.org/jira/browse/YARN-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344114#comment-14344114 ] Brahma Reddy Battula commented on YARN-3204: [~chengbing.liu] Thanks a lot for

[jira] [Updated] (YARN-3275) CapacityScheduler: Preemption happening on non-preemptable queues

[ https://issues.apache.org/jira/browse/YARN-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3275: --- Labels: capacity-scheduler (was: ) > CapacityScheduler: Preemption happening on non-preemptabl

[jira] [Updated] (YARN-3275) CapacityScheduler: Preemption happening on non-preemptable queues

[ https://issues.apache.org/jira/browse/YARN-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3275: --- Summary: CapacityScheduler: Preemption happening on non-preemptable queues (was: Preemption ha

[jira] [Resolved] (YARN-3280) Findbug issue in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-3280. Resolution: Duplicate > Findbug issue in FairScheduler > -- > >

[jira] [Commented] (YARN-2828) Enable auto refresh of web pages (using http parameter)

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

[jira] [Commented] (YARN-3204) Fix new findbug warnings in hadoop-yarn-server-resourcemanager(resourcemanager.scheduler.fair)

[ https://issues.apache.org/jira/browse/YARN-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344151#comment-14344151 ] Karthik Kambatla commented on YARN-3204: Thanks for working on this, [~brahmareddy]

[jira] [Commented] (YARN-3272) Surface container locality info

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

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344160#comment-14344160 ] Allen Wittenauer commented on YARN-3168: bq. Is this planned for branch-2 ? I pers

[jira] [Commented] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344167#comment-14344167 ] Junping Du commented on YARN-3276: -- Just found the PackageInfo in existing TimelineUtils i

[jira] [Updated] (YARN-2380) The normalizeRequests method in SchedulerUtils always resets the vCore to 1

[ https://issues.apache.org/jira/browse/YARN-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2380: - Target Version/s: 2.6.1 > The normalizeRequests method in SchedulerUtils always resets the vCore to 1 > ---

[jira] [Commented] (YARN-1621) Add CLI to list rows of

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344205#comment-14344205 ] Naganarasimha G R commented on YARN-1621: - Hi Bartosz Lugowski, Overall Patch looks

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344218#comment-14344218 ] Masatake Iwasaki commented on YARN-3168: I am going to file a follow-up JIRA to bac

[jira] [Created] (YARN-3285) Convert branch-2 .apt.vm files of YARN to markdown

Masatake Iwasaki created YARN-3285: -- Summary: Convert branch-2 .apt.vm files of YARN to markdown Key: YARN-3285 URL: https://issues.apache.org/jira/browse/YARN-3285 Project: Hadoop YARN Issu

[jira] [Commented] (YARN-2854) The document about timeline service and generic service needs to be updated

[ https://issues.apache.org/jira/browse/YARN-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344224#comment-14344224 ] Naganarasimha G R commented on YARN-2854: - Hi [~jianhe], Thanks for informing but i

[jira] [Updated] (YARN-3272) Surface container locality info

[ https://issues.apache.org/jira/browse/YARN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3272: -- Attachment: YARN-3272.5.patch > Surface container locality info > > >

[jira] [Commented] (YARN-3285) Convert branch-2 .apt.vm files of YARN to markdown

[ https://issues.apache.org/jira/browse/YARN-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344235#comment-14344235 ] Jian He commented on YARN-3285: --- [~iwasakims], thanks for filing this. Otherwise, all docume

[jira] [Commented] (YARN-2380) The normalizeRequests method in SchedulerUtils always resets the vCore to 1

[ https://issues.apache.org/jira/browse/YARN-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344261#comment-14344261 ] Wangda Tan commented on YARN-2380: -- Patch looks good to me, will commit it when Jenkins ge

  1   2   >