[jira] [Commented] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

[ https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270347#comment-14270347 ] Chengbing Liu commented on YARN-2997: - Thanks [~jianhe] ! NM keeps sending

[jira] [Commented] (YARN-3016) (Refactoring) Merge internalAdd/Remove/ReplaceLabels to one method in CommonNodeLabelsManager

[ https://issues.apache.org/jira/browse/YARN-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270518#comment-14270518 ] Rohith commented on YARN-3016: -- It make sense to me. (Refactoring) Merge

[jira] [Commented] (YARN-2807) Option --forceactive not works as described in usage of yarn rmadmin -transitionToActive

[ https://issues.apache.org/jira/browse/YARN-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270522#comment-14270522 ] Akira AJISAKA commented on YARN-2807: - +1, thank you [~iwasakims]. Option

[jira] [Commented] (YARN-2956) Some yarn-site index linked pages are difficult to discover because are not in the side bar

[ https://issues.apache.org/jira/browse/YARN-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270255#comment-14270255 ] Jian He commented on YARN-2956: --- [~iwasakims], thanks for working on this. maybe add a link

[jira] [Commented] (YARN-2996) Refine fs operations in FileSystemRMStateStore and few fixes

[ https://issues.apache.org/jira/browse/YARN-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270274#comment-14270274 ] Yi Liu commented on YARN-2996: -- Thanks [~zjshen] for review and commit. Refine fs operations

[jira] [Created] (YARN-3022) Expose Container resource information from NodeManager for monitoring

Anubhav Dhoot created YARN-3022: --- Summary: Expose Container resource information from NodeManager for monitoring Key: YARN-3022 URL: https://issues.apache.org/jira/browse/YARN-3022 Project: Hadoop YARN

[jira] [Updated] (YARN-810) Support CGroup ceiling enforcement on CPU

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-810: - Attachment: YARN-810-6.patch Update a patch to fix the test failures. Support CGroup ceiling enforcement on CPU

[jira] [Updated] (YARN-313) Add Admin API for supporting node resource configuration in command line

[ https://issues.apache.org/jira/browse/YARN-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-313: Attachment: YARN-313-v3.patch Resync the patch to latest trunk. Add Admin API for supporting node resource

[jira] [Updated] (YARN-3014) Replaces labels on a host should update all NM's labels on that host

[ https://issues.apache.org/jira/browse/YARN-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3014: - Attachment: YARN-3014-2.patch Thanks [~jianhe]'s review, addressed comments and also updated test cases to

[jira] [Created] (YARN-3023) Race condition in ZKRMStateStore#createWithRetries from ZooKeeper cause RM crash

zhihai xu created YARN-3023: --- Summary: Race condition in ZKRMStateStore#createWithRetries from ZooKeeper cause RM crash Key: YARN-3023 URL: https://issues.apache.org/jira/browse/YARN-3023 Project: Hadoop

[jira] [Commented] (YARN-3014) Replaces labels on a host should update all NM's labels on that host

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

[jira] [Commented] (YARN-810) Support CGroup ceiling enforcement on CPU

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

[jira] [Commented] (YARN-313) Add Admin API for supporting node resource configuration in command line

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

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.001.patch Initial patch based on YARN-2984 which adds metrics for Containers

[jira] [Commented] (YARN-2637) maximum-am-resource-percent could be respected for both LeafQueue/User when trying to activate applications.

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

[jira] [Commented] (YARN-3023) Race condition in ZKRMStateStore#createWithRetries from ZooKeeper cause RM crash

[ https://issues.apache.org/jira/browse/YARN-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270526#comment-14270526 ] Rohith commented on YARN-3023: -- Which version of Hadoop are you using? In trunk this is

[jira] [Updated] (YARN-2807) Option --forceactive not works as described in usage of yarn rmadmin -transitionToActive

[ https://issues.apache.org/jira/browse/YARN-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-2807: Hadoop Flags: Reviewed Option --forceactive not works as described in usage of yarn rmadmin

[jira] [Commented] (YARN-3023) Race condition in ZKRMStateStore#createWithRetries from ZooKeeper cause RM crash

[ https://issues.apache.org/jira/browse/YARN-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270581#comment-14270581 ] zhihai xu commented on YARN-3023: - Yes, you are right. The issue is the same as YARN-2721.

[jira] [Resolved] (YARN-3023) Race condition in ZKRMStateStore#createWithRetries from ZooKeeper cause RM crash

[ https://issues.apache.org/jira/browse/YARN-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu resolved YARN-3023. - Resolution: Duplicate Race condition in ZKRMStateStore#createWithRetries from ZooKeeper cause RM crash

[jira] [Updated] (YARN-3024) LocalizerRunner should give DIE action when all resources are localized

[ https://issues.apache.org/jira/browse/YARN-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengbing Liu updated YARN-3024: Attachment: YARN-3024.02.patch Fixed tests accordingly. LocalizerRunner should give DIE action

[jira] [Commented] (YARN-2141) [Umbrella] Capture container and node resource consumption

[ https://issues.apache.org/jira/browse/YARN-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270535#comment-14270535 ] Vinod Kumar Vavilapalli commented on YARN-2141: --- One other related effort is

[jira] [Commented] (YARN-2984) Metrics for container's actual memory usage

[ https://issues.apache.org/jira/browse/YARN-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270536#comment-14270536 ] Vinod Kumar Vavilapalli commented on YARN-2984: --- Linking related efforts.

[jira] [Updated] (YARN-2637) maximum-am-resource-percent could be respected for both LeafQueue/User when trying to activate applications.

[ https://issues.apache.org/jira/browse/YARN-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-2637: -- Attachment: YARN-2637.36.patch Should be down to one failing test, let's see

[jira] [Commented] (YARN-3019) Enable RM work-preserving restart by default

[ https://issues.apache.org/jira/browse/YARN-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270087#comment-14270087 ] Allen Wittenauer commented on YARN-3019: I'm not in favor of this going into

[jira] [Commented] (YARN-3019) Enable RM work-preserving restart by default

[ https://issues.apache.org/jira/browse/YARN-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270100#comment-14270100 ] Jian He commented on YARN-3019: --- To clarify: this jira is to flip recovery mode to

[jira] [Commented] (YARN-1680) availableResources sent to applicationMaster in heartbeat should exclude blacklistedNodes free memory.

[ https://issues.apache.org/jira/browse/YARN-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270110#comment-14270110 ] Chen He commented on YARN-1680: --- Thank you for the comments, [~jlowe]. [~cwelch] created

[jira] [Created] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

Harsh J created YARN-3021: - Summary: YARN's delegation-token handling disallows certain trust setups to operate properly Key: YARN-3021 URL: https://issues.apache.org/jira/browse/YARN-3021 Project: Hadoop

[jira] [Commented] (YARN-2637) maximum-am-resource-percent could be respected for both LeafQueue/User when trying to activate applications.

[ https://issues.apache.org/jira/browse/YARN-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270116#comment-14270116 ] Jian He commented on YARN-2637: --- Quick thing, YARN-3010 fixed the find bug warning. the

[jira] [Updated] (YARN-3019) Enable RM work-preserving restart by default

[ https://issues.apache.org/jira/browse/YARN-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3019: -- Description: The proposal is to set yarn.resourcemanager.work-preserving-recovery.enabled to true by default

[jira] [Commented] (YARN-3014) Replaces labels on a host should update all NM's labels on that host

[ https://issues.apache.org/jira/browse/YARN-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270179#comment-14270179 ] Jian He commented on YARN-3014: --- addLabel and removeLabel on the Host should not do

[jira] [Commented] (YARN-3010) Fix recent findbug issue in AbstractYarnScheduler

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

[jira] [Commented] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

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

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

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

[jira] [Commented] (YARN-2936) YARNDelegationTokenIdentifier doesn't set proto.builder now

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

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

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

[jira] [Commented] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

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

[jira] [Commented] (YARN-2936) YARNDelegationTokenIdentifier doesn't set proto.builder now

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

[jira] [Commented] (YARN-3010) Fix recent findbug issue in AbstractYarnScheduler

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

[jira] [Assigned] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3018: --- Assignee: nijel Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and

[jira] [Commented] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

[ https://issues.apache.org/jira/browse/YARN-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269058#comment-14269058 ] nijel commented on YARN-3018: - Please give your opinion. I prefer to have the value as -1 in

[jira] [Created] (YARN-3018) Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file

nijel created YARN-3018: --- Summary: Unify the default value for yarn.scheduler.capacity.node-locality-delay in code and default xml file Key: YARN-3018 URL: https://issues.apache.org/jira/browse/YARN-3018

[jira] [Commented] (YARN-2996) Refine fs operations in FileSystemRMStateStore and few fixes

[ https://issues.apache.org/jira/browse/YARN-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269728#comment-14269728 ] Zhijie Shen commented on YARN-2996: --- +1. The test failure seems not to be related. Will

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

[ https://issues.apache.org/jira/browse/YARN-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269720#comment-14269720 ] Zhijie Shen commented on YARN-2880: --- Is

[jira] [Commented] (YARN-2996) Refine fs operations in FileSystemRMStateStore and few fixes

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

[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-tabpanelfocusedCommentId=14269784#comment-14269784 ] Mayank Bansal commented on YARN-2933: - Thanks [~wangda] and Sunil for review. bq. In

[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] [Updated] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2421: -- Target Version/s: 2.7.0 (was: 2.6.0) CapacityScheduler still allocates containers to an app in the FINISHING

[jira] [Updated] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[ https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2786: - Attachment: (was: YARN-2800-20141118-1.patch) Create yarn cluster CLI to enable list node labels

[jira] [Updated] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[ https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2786: - Attachment: YARN-2786-20150108-1-full.patch Create yarn cluster CLI to enable list node labels collection

[jira] [Updated] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[ https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2786: - Attachment: YARN-2800-20141118-1.patch Create yarn cluster CLI to enable list node labels collection

[jira] [Updated] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[ https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2786: - Attachment: YARN-2786-20150108-1-without-yarn.cmd.patch Updated patch addressed comments from [~aw

[jira] [Commented] (YARN-3016) (Refactoring) Merge internalAdd/Remove/ReplaceLabels to one method in CommonNodeLabelsManager

[ https://issues.apache.org/jira/browse/YARN-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269824#comment-14269824 ] Wangda Tan commented on YARN-3016: -- I meant CommonNodeLabelsManager, methods start with

[jira] [Commented] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

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

[jira] [Commented] (YARN-3010) Fix recent findbug issue in AbstractYarnScheduler

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

[jira] [Commented] (YARN-2936) YARNDelegationTokenIdentifier doesn't set proto.builder now

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

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

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

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269373#comment-14269373 ] Andrew Johnson commented on YARN-2893: -- Yeah, that definitely seems like its worth a

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

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

[jira] [Commented] (YARN-3010) Fix recent findbug issue in AbstractYarnScheduler

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

[jira] [Commented] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

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

[jira] [Commented] (YARN-3010) Fix recent findbug issue in AbstractYarnScheduler

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

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

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

[jira] [Commented] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

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

[jira] [Commented] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

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

[jira] [Commented] (YARN-3010) Fix recent findbug issue in AbstractYarnScheduler

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

[jira] [Commented] (YARN-2936) YARNDelegationTokenIdentifier doesn't set proto.builder now

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

[jira] [Commented] (YARN-2571) RM to support YARN registry

[ https://issues.apache.org/jira/browse/YARN-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269548#comment-14269548 ] Steve Loughran commented on YARN-2571: -- Vinod, having the RM create the user paths

[jira] [Commented] (YARN-2936) YARNDelegationTokenIdentifier doesn't set proto.builder now

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

[jira] [Commented] (YARN-2936) YARNDelegationTokenIdentifier doesn't set proto.builder now

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

[jira] [Commented] (YARN-2880) Add a test in TestRMRestart to make sure node labels will be recovered if it is enabled

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

[jira] [Commented] (YARN-2571) RM to support YARN registry

[ https://issues.apache.org/jira/browse/YARN-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269556#comment-14269556 ] Steve Loughran commented on YARN-2571: -- Xuan 1. If you can show me an example of an

[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-tabpanelfocusedCommentId=14269836#comment-14269836 ] Wangda Tan commented on YARN-2933: -- [~mayank_bansal], Thanks for updating the patch, bq.

[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-tabpanelfocusedCommentId=14269858#comment-14269858 ] Jian He commented on YARN-2933: --- one other comment: getNodeLabels is not used anywhere, we

[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-tabpanelfocusedCommentId=14269868#comment-14269868 ] Sunil G commented on YARN-2933: --- Hi [~mayank_bansal] Thank you for the clarification. I have

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

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12690906/YARN-2786-20150108-1-without-yarn.cmd.patch against trunk revision 20625c8. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color

[jira] [Updated] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are acked

[ https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2997: -- Summary: NM keeps sending already-sent completed containers to RM until containers are acked (was: NM keeps

[jira] [Updated] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

[ https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2997: -- Summary: NM keeps sending already-sent completed containers to RM until containers are removed from context

[jira] [Commented] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

[ https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269885#comment-14269885 ] Jian He commented on YARN-2997: --- patch looks good to me. NM keeps sending already-sent

[jira] [Commented] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

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

[jira] [Updated] (YARN-3014) Replaces labels on a host should update all NM's labels on that host

[ https://issues.apache.org/jira/browse/YARN-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3014: - Summary: Replaces labels on a host should update all NM's labels on that host (was: Changing labels on a

[jira] [Updated] (YARN-3014) Changing labels on a host should update all NM's labels on that host

[ https://issues.apache.org/jira/browse/YARN-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3014: - Attachment: YARN-3014-1.patch Attached patch, and kick jenkins. This patch contains refactoring described

[jira] [Commented] (YARN-3015) yarn classpath command should support same options as hadoop classpath.

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

[jira] [Resolved] (YARN-712) RMDelegationTokenSecretManager shouldn't start in non-secure mode

[ https://issues.apache.org/jira/browse/YARN-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-712. -- Resolution: Won't Fix RMDelegationTokenSecretManager shouldn't start in non-secure mode

[jira] [Created] (YARN-3019) Enable work-preserving restart by default

Jian He created YARN-3019: - Summary: Enable work-preserving restart by default Key: YARN-3019 URL: https://issues.apache.org/jira/browse/YARN-3019 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-3019) Enable RM work-preserving restart by default

[ https://issues.apache.org/jira/browse/YARN-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3019: -- Summary: Enable RM work-preserving restart by default (was: Enable work-preserving restart by default )

[jira] [Created] (YARN-3020) n similar addContainerRequest()s produce n*(n+1)/2 containers

Peter D Kirchner created YARN-3020: -- Summary: n similar addContainerRequest()s produce n*(n+1)/2 containers Key: YARN-3020 URL: https://issues.apache.org/jira/browse/YARN-3020 Project: Hadoop YARN

[jira] [Commented] (YARN-3014) Replaces labels on a host should update all NM's labels on that host

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

[jira] [Commented] (YARN-2141) [Umbrella] Capture container and node resource consumption

[ https://issues.apache.org/jira/browse/YARN-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269919#comment-14269919 ] Vinod Kumar Vavilapalli commented on YARN-2141: --- Related to and very likely a

[jira] [Commented] (YARN-2984) Metrics for container's actual memory usage

[ https://issues.apache.org/jira/browse/YARN-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269944#comment-14269944 ] Anubhav Dhoot commented on YARN-2984: - Seems good. I tested it and shows up on the jmx

[jira] [Commented] (YARN-1798) TestContainerLaunch, TestContainersMonitor, TestNodeManagerShutdown, TestNodeStatusUpdater fails on Linux

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

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12690906/YARN-2786-20150108-1-without-yarn.cmd.patch against trunk revision 708b1aa. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color

[jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

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

[jira] [Commented] (YARN-1798) TestContainerLaunch, TestContainersMonitor, TestNodeManagerShutdown, TestNodeStatusUpdater fails on Linux

[ https://issues.apache.org/jira/browse/YARN-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269940#comment-14269940 ] Jian He commented on YARN-1798: --- I think the issue is outdated now, may be close?

[jira] [Updated] (YARN-3015) yarn classpath command should support same options as hadoop classpath.

[ https://issues.apache.org/jira/browse/YARN-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3015: --- Attachment: YARN-3015.001.patch yarn classpath command should support same options as hadoop

[jira] [Commented] (YARN-2965) Enhance Node Managers to monitor and report the resource usage on machines

[ https://issues.apache.org/jira/browse/YARN-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269921#comment-14269921 ] Vinod Kumar Vavilapalli commented on YARN-2965: --- Linking all related efforts.

[jira] [Commented] (YARN-2745) Extend YARN to support multi-resource packing of tasks

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269926#comment-14269926 ] Vinod Kumar Vavilapalli commented on YARN-2745: --- Haven't read the design doc