[jira] [Updated] (YARN-7004) Add configs cache to optimize refreshQueues performance for large scale queues

[ https://issues.apache.org/jira/browse/YARN-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-7004: --- Attachment: YARN-7004.001.patch Uploaded v1 patch for review. > Add configs cache to optimize refreshQueues

[jira] [Created] (YARN-7004) Add configs cache to optimize refreshQueues performance for large scale queues

Tao Yang created YARN-7004: -- Summary: Add configs cache to optimize refreshQueues performance for large scale queues Key: YARN-7004 URL: https://issues.apache.org/jira/browse/YARN-7004 Project: Hadoop YARN

[jira] [Updated] (YARN-7003) DRAINING state of queues can't be recovered after RM restart

[ https://issues.apache.org/jira/browse/YARN-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-7003: --- Attachment: YARN-7003.001.patch > DRAINING state of queues can't be recovered after RM restart >

[jira] [Assigned] (YARN-7003) DRAINING state of queues can't be recovered after RM restart

[ https://issues.apache.org/jira/browse/YARN-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-7003: --- Assignee: Tao Yang > DRAINING state of queues can't be recovered after RM restart >

[jira] [Updated] (YARN-7003) DRAINING state of queues can't be recovered after RM restart

[ https://issues.apache.org/jira/browse/YARN-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-7003: --- Affects Version/s: (was: 3.0.0-alpha3) 3.0.0-alpha4 > DRAINING state of queues

[jira] [Updated] (YARN-7003) DRAINING state of queues can't be recovered after RM restart

[ https://issues.apache.org/jira/browse/YARN-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-7003: --- Affects Version/s: 2.9.0 > DRAINING state of queues can't be recovered after RM restart >

[jira] [Created] (YARN-7003) DRAINING state of queues can't be recovered after RM restart

Tao Yang created YARN-7003: -- Summary: DRAINING state of queues can't be recovered after RM restart Key: YARN-7003 URL: https://issues.apache.org/jira/browse/YARN-7003 Project: Hadoop YARN Issue

[jira] [Resolved] (YARN-6044) Resource bar of Capacity Scheduler UI does not show correctly

[ https://issues.apache.org/jira/browse/YARN-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang resolved YARN-6044. Resolution: Duplicate > Resource bar of Capacity Scheduler UI does not show correctly >

[jira] [Commented] (YARN-6044) Resource bar of Capacity Scheduler UI does not show correctly

[ https://issues.apache.org/jira/browse/YARN-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124767#comment-16124767 ] Tao Yang commented on YARN-6044: Thanks [~djp] and [~sunilg] for your reply. The solution makes sense to

[jira] [Commented] (YARN-4522) Queue acl can be checked at app submission

[ https://issues.apache.org/jira/browse/YARN-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124763#comment-16124763 ] Naganarasimha G R commented on YARN-4522: - [~bibinchundatt], Agree with your point, I think you can

[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed

[ https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124762#comment-16124762 ] Naganarasimha G R commented on YARN-65: --- Thanks [~rohithsharma] & [~bibinchundatt], for sharing your

[jira] [Commented] (YARN-6741) Deleting all children of a Parent Queue on refresh throws exception

[ https://issues.apache.org/jira/browse/YARN-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124758#comment-16124758 ] Naganarasimha G R commented on YARN-6741: - [~bibinchundatt], Locally these test *time outs* seems

[jira] [Updated] (YARN-6999) Add log about how to solve Error: Could not find or load main class org.apache.hadoop.mapreduce.v2.app.MRAppMaster

[ https://issues.apache.org/jira/browse/YARN-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Linlin Zhou updated YARN-6999: -- Attachment: yarn-6999.patch > Add log about how to solve Error: Could not find or load main class >

[jira] [Commented] (YARN-6972) Adding RM ClusterId in AppInfo

[ https://issues.apache.org/jira/browse/YARN-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124658#comment-16124658 ] Hadoop QA commented on YARN-6972: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-6972) Adding RM ClusterId in AppInfo

[ https://issues.apache.org/jira/browse/YARN-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Nayak updated YARN-6972: -- Attachment: YARN-6972.006.patch That failed test was actually relevant, which should be fixed in the v6

[jira] [Commented] (YARN-6629) NPE occurred when container allocation proposal is applied but its resource requests are removed before

[ https://issues.apache.org/jira/browse/YARN-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124630#comment-16124630 ] Hadoop QA commented on YARN-6629: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-6629) NPE occurred when container allocation proposal is applied but its resource requests are removed before

[ https://issues.apache.org/jira/browse/YARN-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-6629: --- Attachment: YARN-6629.002.patch Uploaded a new patch with test case. > NPE occurred when container allocation

[jira] [Commented] (YARN-6629) NPE occurred when container allocation proposal is applied but its resource requests are removed before

[ https://issues.apache.org/jira/browse/YARN-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124569#comment-16124569 ] Tao Yang commented on YARN-6629: Sorry for the late reply. Thanks [~sunilg] for reviewing this issue. Yes,

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124564#comment-16124564 ] Shane Kumpf commented on YARN-6930: --- Thanks [~miklos.szeg...@cloudera.com] and [~ebadger] for the

[jira] [Commented] (YARN-6257) CapacityScheduler REST API produces incorrect JSON - JSON object operationsInfo contains deplicate key

[ https://issues.apache.org/jira/browse/YARN-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124563#comment-16124563 ] Tao Yang commented on YARN-6257: [~leftnoteasy], thanks for the reply. Yes, duplicated keys in JSON object

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124561#comment-16124561 ] Hadoop QA commented on YARN-6930: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-6930: -- Attachment: YARN-6930.003.patch > Admins should be able to explicitly enable specific

[jira] [Commented] (YARN-6880) FSQueue.reservedResource can be final

[ https://issues.apache.org/jira/browse/YARN-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124528#comment-16124528 ] HondaWei commented on YARN-6880: Hi Daniel , I would like to take this task, thank you very much! >