[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541730#comment-14541730 ] Junping Du commented on YARN-3411: -- Sure. Cancel the patch until we have new version. Thx!

[jira] [Created] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

Rohith created YARN-3640: Summary: NodeManager JVM continues to run after SHUTDOWN event is triggered. Key: YARN-3640 URL: https://issues.apache.org/jira/browse/YARN-3640 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541742#comment-14541742 ] Rohith commented on YARN-3640: -- It looks similar, but I did not get how did you taken *jni

[jira] [Updated] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-160: --- Attachment: YARN-160.007.patch Uploaded 007.patch which improves some logging. nodemanagers should

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541751#comment-14541751 ] Peng Zhang commented on YARN-3640: -- I use pstack to get it NodeManager JVM continues to

[jira] [Updated] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated YARN-3638: -- Component/s: yarn scheduler resourcemanager

[jira] [Updated] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3639: -- Assignee: (was: Xianyin Xin) It takes too long time for RM to recover all apps if the original

[jira] [Updated] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3640: - Attachment: hadoop-rohith-nodemanager-test123.log Attached the nodemanager log file. It contains log from stopping

[jira] [Commented] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

[ https://issues.apache.org/jira/browse/YARN-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541722#comment-14541722 ] Junping Du commented on YARN-3634: -- Thanks [~sjlee0] to report the issue and deliver the

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541743#comment-14541743 ] Rohith commented on YARN-3640: -- I missed this issue, thanks for pointing out. NodeManager

[jira] [Updated] (YARN-2921) MockRM#waitForState methods can be too slow and flaky

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-2921: - Attachment: YARN-2921.008.patch Resubmitting a patch again. MockRM#waitForState methods can be

[jira] [Commented] (YARN-2921) MockRM#waitForState methods can be too slow and flaky

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

[jira] [Created] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

Xianyin Xin created YARN-3639: - Summary: It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node. Key: YARN-3639 URL:

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

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

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541592#comment-14541592 ] Tsuyoshi Ozawa commented on YARN-2336: -- I see. Should we remove childQueue when

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541612#comment-14541612 ] Steve Loughran commented on YARN-1039: -- +1 for a long-lived bit. Services can set the

[jira] [Created] (YARN-3638) Yarn Scheduler show percentage of total cluster that a queue is using

Hari Sekhon created YARN-3638: - Summary: Yarn Scheduler show percentage of total cluster that a queue is using Key: YARN-3638 URL: https://issues.apache.org/jira/browse/YARN-3638 Project: Hadoop YARN

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541705#comment-14541705 ] Varun Vasudev commented on YARN-3591: - [~zxu], [~lavkesh] - instead of checking listing

[jira] [Updated] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3640: - Attachment: nm_143.out nm_141.out Attaching the thread of 2 NM's. NodeManager JVM continues to

[jira] [Updated] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated YARN-3638: -- Summary: Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is

[jira] [Updated] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated YARN-3638: -- Description: Request to show % of total cluster resources each queue is currently consuming for jobs on

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541669#comment-14541669 ] Junping Du commented on YARN-41: bq. In the case of work-preserving NM restart (or under

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541697#comment-14541697 ] nijel commented on YARN-3639: - hi [~xinxianyin] Thanks for reporting this issue. Can you attach

[jira] [Commented] (YARN-2921) MockRM#waitForState methods can be too slow and flaky

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541734#comment-14541734 ] Tsuyoshi Ozawa commented on YARN-2921: -- [~leftnoteasy] all tests are green. Could you

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541733#comment-14541733 ] Peng Zhang commented on YARN-3640: -- I'v encounter the same problem, and filed YARN-3585.

[jira] [Resolved] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-3640. -- Resolution: Duplicate Closing as duplicate. NodeManager JVM continues to run after SHUTDOWN event is

[jira] [Updated] (YARN-3617) Fix unused variable to get CPU frequency on Windows systems

[ https://issues.apache.org/jira/browse/YARN-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated YARN-3617: - Attachment: YARN-3617.1.patch Attached an initial patch. Please review. Fix unused variable to get CPU

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541899#comment-14541899 ] Hadoop QA commented on YARN-3170: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3641: - Component/s: rolling upgrade nodemanager Affects Version/s: 2.6.0

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541846#comment-14541846 ] Brahma Reddy Battula commented on YARN-3170: Thanks [~ozawa] for reminding ..

[jira] [Commented] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541845#comment-14541845 ] Brahma Reddy Battula commented on YARN-3170: Thanks [~ozawa] for reminding ..

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541881#comment-14541881 ] Jason Lowe commented on YARN-41: In light of NM restart, one of the problems with having the

[jira] [Commented] (YARN-3489) RMServerUtils.validateResourceRequests should only obtain queue info once

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

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541861#comment-14541861 ] Varun Vasudev commented on YARN-160: The test failure is unrelated to the patch.

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3641: - Description: If NM' services not get stopped properly, we cannot start NM with enabling NM restart with

[jira] [Updated] (YARN-3579) getLabelsToNodes in CommonNodeLabelsManager should support NodeLabel instead of label name as String

[ https://issues.apache.org/jira/browse/YARN-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3579: -- Attachment: 0004-YARN-3579.patch Updating patch after a compilation problem. getLabelsToNodes in

[jira] [Created] (YARN-3641) stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

Junping Du created YARN-3641: Summary: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services. Key: YARN-3641 URL: https://issues.apache.org/jira/browse/YARN-3641

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3641: - Attachment: YARN-3641.patch Upload a quick patch to fix it. The issue is obviously and the solution is

[jira] [Commented] (YARN-3627) Preemption not triggered in Fair scheduler when maxResources is set on parent queue

[ https://issues.apache.org/jira/browse/YARN-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541782#comment-14541782 ] Bibin A Chundatt commented on YARN-3627: Hi [~kasha] Thank you for looking into the

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541772#comment-14541772 ] Hudson commented on YARN-3613: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #195 (See

[jira] [Commented] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API

[ https://issues.apache.org/jira/browse/YARN-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541773#comment-14541773 ] Hudson commented on YARN-3539: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #195 (See

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541785#comment-14541785 ] Junping Du commented on YARN-3505: -- Latest patch LGTM. [~jianhe], about your previous

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541794#comment-14541794 ] Hudson commented on YARN-3613: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #926 (See

[jira] [Commented] (YARN-3513) Remove unused variables in ContainersMonitorImpl and add debug log for overall resource usage by all containers

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541799#comment-14541799 ] Hudson commented on YARN-3513: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #926 (See

[jira] [Commented] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API

[ https://issues.apache.org/jira/browse/YARN-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541795#comment-14541795 ] Hudson commented on YARN-3539: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #926 (See

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541802#comment-14541802 ] Hudson commented on YARN-3629: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #926 (See

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

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

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541780#comment-14541780 ] Hudson commented on YARN-3629: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #195 (See

[jira] [Commented] (YARN-3513) Remove unused variables in ContainersMonitorImpl and add debug log for overall resource usage by all containers

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541777#comment-14541777 ] Hudson commented on YARN-3513: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #195 (See

[jira] [Commented] (YARN-3640) NodeManager JVM continues to run after SHUTDOWN event is triggered.

[ https://issues.apache.org/jira/browse/YARN-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541790#comment-14541790 ] Rohith commented on YARN-3640: -- I am able to reproduce this always..!!! NodeManager JVM

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541812#comment-14541812 ] Peng Zhang commented on YARN-3585: -- As YARN-3640, Rohith has encountered the same problem.

[jira] [Updated] (YARN-3170) YARN architecture document needs updating

[ https://issues.apache.org/jira/browse/YARN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3170: --- Attachment: YARN-3170-006.patch YARN architecture document needs updating

[jira] [Commented] (YARN-3617) Fix unused variable to get CPU frequency on Windows systems

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

[jira] [Updated] (YARN-3489) RMServerUtils.validateResourceRequests should only obtain queue info once

[ https://issues.apache.org/jira/browse/YARN-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3489: --- Attachment: YARN-3489-branch-2.7.02.patch RMServerUtils.validateResourceRequests should only obtain

[jira] [Commented] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541885#comment-14541885 ] Jason Lowe commented on YARN-3638: -- Isn't this the Absolute Used Capacity metric that is

[jira] [Commented] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541950#comment-14541950 ] Hari Sekhon commented on YARN-3638: --- [~jlowe] yes I believe it is % of absolute capacity

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541980#comment-14541980 ] Hudson commented on YARN-3629: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2124 (See

[jira] [Commented] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API

[ https://issues.apache.org/jira/browse/YARN-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541973#comment-14541973 ] Hudson commented on YARN-3539: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2124 (See

[jira] [Commented] (YARN-3629) NodeID is always printed as null in node manager initialization log.

[ https://issues.apache.org/jira/browse/YARN-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541999#comment-14541999 ] Hudson commented on YARN-3629: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #184 (See

[jira] [Commented] (YARN-3539) Compatibility doc to state that ATS v1 is a stable REST API

[ https://issues.apache.org/jira/browse/YARN-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541993#comment-14541993 ] Hudson commented on YARN-3539: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #184 (See

[jira] [Commented] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541969#comment-14541969 ] Jason Lowe commented on YARN-3638: -- bq. I believe it is % of absolute capacity that is

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541972#comment-14541972 ] Hudson commented on YARN-3613: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2124 (See

[jira] [Commented] (YARN-3579) getLabelsToNodes in CommonNodeLabelsManager should support NodeLabel instead of label name as String

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

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542000#comment-14542000 ] Jason Lowe commented on YARN-3641: -- I think the patch approach is OK, but I'm not sure I

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542028#comment-14542028 ] Junping Du commented on YARN-3641: -- bq. We kill -9 the NM during rolling upgrades, which

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542045#comment-14542045 ] Junping Du commented on YARN-41: Thanks [~jlowe] for sharing this prospective. I think

[jira] [Commented] (YARN-3628) ContainerMetrics should support always-flush mode.

[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542036#comment-14542036 ] Karthik Kambatla commented on YARN-3628: bq. So the empty content is shown for the

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542078#comment-14542078 ] Devaraj K commented on YARN-3585: - Thanks for reply. I have enabled NM recovery in my env.

[jira] [Commented] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

[ https://issues.apache.org/jira/browse/YARN-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541992#comment-14541992 ] Hudson commented on YARN-3613: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #184 (See

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

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

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542051#comment-14542051 ] Jason Lowe commented on YARN-41: I think avoiding the unregister during shutdown _if_ the NM

[jira] [Updated] (YARN-3628) ContainerMetrics should support always-flush mode.

[ https://issues.apache.org/jira/browse/YARN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3628: Issue Type: Improvement (was: Bug) ContainerMetrics should support always-flush mode.

[jira] [Commented] (YARN-3638) Yarn Resource Manager Scheduler page - show percentage of total cluster that each queue is using

[ https://issues.apache.org/jira/browse/YARN-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542563#comment-14542563 ] Wangda Tan commented on YARN-3638: -- I think this is useful. Maybe one possible way is add

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

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

[jira] [Created] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

Lee Hounshell created YARN-3642: --- Summary: Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java Key: YARN-3642 URL: https://issues.apache.org/jira/browse/YARN-3642 Project: Hadoop

[jira] [Resolved] (YARN-2221) WebUI: RM scheduler page's queue filter status will affect appllication page

[ https://issues.apache.org/jira/browse/YARN-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-2221. - Resolution: Duplicate WebUI: RM scheduler page's queue filter status will affect appllication page

[jira] [Commented] (YARN-2221) WebUI: RM scheduler page's queue filter status will affect appllication page

[ https://issues.apache.org/jira/browse/YARN-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542390#comment-14542390 ] Xuan Gong commented on YARN-2221: - Actually, they are duplicate. Close this ticket as

[jira] [Updated] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3585: -- Priority: Critical (was: Major) Target Version/s: 2.7.1 Marking it

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3641: -- Target Version/s: 2.7.1 (was: 2.8.0) Marking it as critical for 2.7.1 whichever

[jira] [Commented] (YARN-3634) TestMRTimelineEventHandling and TestApplication are broken

[ https://issues.apache.org/jira/browse/YARN-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542423#comment-14542423 ] Sangjin Lee commented on YARN-3634: --- Thanks [~djp]! TestMRTimelineEventHandling and

[jira] [Updated] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3626: -- Attachment: YARN-3626.6.patch Fix broken unit tests On Windows localized resources are not moved to

[jira] [Commented] (YARN-3585) Nodemanager cannot exit when decommission with NM recovery enabled

[ https://issues.apache.org/jira/browse/YARN-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542432#comment-14542432 ] Jason Lowe commented on YARN-3585: -- This is very likely a case where the leveldb state

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542430#comment-14542430 ] Vinod Kumar Vavilapalli commented on YARN-41: - It will be a much easier

[jira] [Assigned] (YARN-3643) Provide a way to store only running applications in the state store

[ https://issues.apache.org/jira/browse/YARN-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-3643: -- Assignee: Varun Saxena Provide a way to store only running applications in the state store

[jira] [Updated] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2921: - Summary: Fix MockRM/MockAM#waitForState sleep too long (was: MockRM#waitForState methods can be too slow

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542609#comment-14542609 ] Xuan Gong commented on YARN-3626: - Committed into trunk/branch-2/branch-2.7. Thanks, Craig.

[jira] [Updated] (YARN-3579) CommonNodeLabelsManager should support NodeLabel instead of string label name when getting node-to-label/label-to-label mappings

[ https://issues.apache.org/jira/browse/YARN-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3579: - Summary: CommonNodeLabelsManager should support NodeLabel instead of string label name when getting

[jira] [Updated] (YARN-3521) Support return structured NodeLabel objects in REST API

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3521: - Summary: Support return structured NodeLabel objects in REST API (was: Support return structured

[jira] [Commented] (YARN-2921) Fix MockRM/MockAM#waitForState sleep too long

[ https://issues.apache.org/jira/browse/YARN-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542678#comment-14542678 ] Karthik Kambatla commented on YARN-2921: Thanks Tsuyoshi for fixing this. Just

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542747#comment-14542747 ] Wangda Tan commented on YARN-3630: -- +1 for the general idea, [~xinxianyin], I think one

[jira] [Commented] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and namenode is deployed on the same node.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543187#comment-14543187 ] Xianyin Xin commented on YARN-3639: --- Yes, you're right [~aw]. It takes too long time

[jira] [Updated] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and NN go down at the same time.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3639: -- Summary: It takes too long time for RM to recover all apps if the original active RM and NN go down at

[jira] [Assigned] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA reassigned YARN-2336: --- Assignee: Akira AJISAKA (was: Kenji Kikushima) Fair scheduler REST api returns a missing

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543192#comment-14543192 ] Akira AJISAKA commented on YARN-2336: - bq. Should we remove childQueue when childQueue

[jira] [Updated] (YARN-3639) It takes too long time for RM to recover all apps if the original active RM and NN go down at the same time.

[ https://issues.apache.org/jira/browse/YARN-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3639: -- Description: If the active RM and NN go down at the same time, the new RM will take long time to recover

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543198#comment-14543198 ] Rohith commented on YARN-3641: -- Apologies for coming late into this JIRA.. I think

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542598#comment-14542598 ] Xuan Gong commented on YARN-3626: - +1 LGTM. Will commit On Windows localized resources

[jira] [Updated] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3632: --- Component/s: capacityscheduler Ordering policy should be allowed to reorder an application

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542694#comment-14542694 ] Hudson commented on YARN-3521: -- FAILURE: Integrated in Hadoop-trunk-Commit #7821 (See

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542742#comment-14542742 ] Hudson commented on YARN-3641: -- SUCCESS: Integrated in Hadoop-trunk-Commit #7823 (See

  1   2   3   >