[jira] [Created] (YARN-2679) add container launch prepare time metrics to NM.

zhihai xu created YARN-2679: --- Summary: add container launch prepare time metrics to NM. Key: YARN-2679 URL: https://issues.apache.org/jira/browse/YARN-2679 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-2679) add container launch prepare time metrics to NM.

[ https://issues.apache.org/jira/browse/YARN-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2679: Attachment: YARN-2679.000.patch add container launch prepare time metrics to NM.

[jira] [Updated] (YARN-2636) Windows Secure Container Executor: add unit tests for WSCE

[ https://issues.apache.org/jira/browse/YARN-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2636: --- Attachment: YARN-2636.delta.1.patch delta.1.path requires YARN-2198. Adds new unit test for

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169132#comment-14169132 ] Remus Rusanu commented on YARN-2198: [~cwelch] I have added the suggested WSCE unit

[jira] [Created] (YARN-2680) Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is enabled.

Junping Du created YARN-2680: Summary: Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is enabled. Key: YARN-2680 URL: https://issues.apache.org/jira/browse/YARN-2680

[jira] [Updated] (YARN-2680) Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is enabled.

[ https://issues.apache.org/jira/browse/YARN-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2680: - Assignee: (was: Junping Du) Node shouldn't be listed as RUNNING when NM daemon is stop even when

[jira] [Created] (YARN-2681) Support bandwidth enforcement for containers while reading from HDFS

cntic created YARN-2681: --- Summary: Support bandwidth enforcement for containers while reading from HDFS Key: YARN-2681 URL: https://issues.apache.org/jira/browse/YARN-2681 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2681) Support bandwidth enforcement for containers while reading from HDFS

[ https://issues.apache.org/jira/browse/YARN-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cntic updated YARN-2681: Description: To read/write data from HDFS on data node, applications establise TCP/IP connections with the

[jira] [Updated] (YARN-2681) Support bandwidth enforcement for containers while reading from HDFS

[ https://issues.apache.org/jira/browse/YARN-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cntic updated YARN-2681: Description: To read/write data from HDFS on data node, applications establise TCP/IP connections with the

[jira] [Updated] (YARN-2681) Support bandwidth enforcement for containers while reading from HDFS

[ https://issues.apache.org/jira/browse/YARN-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cntic updated YARN-2681: Attachment: Traffic Control Design.png Support bandwidth enforcement for containers while reading from HDFS

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169211#comment-14169211 ] Naganarasimha G R commented on YARN-2495: - hi [~wangda] [~aw] , Few queries : Some

[jira] [Commented] (YARN-2680) Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is enabled.

[ https://issues.apache.org/jira/browse/YARN-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169289#comment-14169289 ] Jason Lowe commented on YARN-2680: -- [~djp] could you elaborate more on the use-case?

[jira] [Commented] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169299#comment-14169299 ] Karthik Kambatla commented on YARN-2641: bq. If NodeListManager#refreshNodes

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169302#comment-14169302 ] Karthik Kambatla commented on YARN-2566: Submitted patch to kick off Jenkins.

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

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

[jira] [Updated] (YARN-2667) Fix the release audit warning caused by hadoop-yarn-registry

[ https://issues.apache.org/jira/browse/YARN-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2667: - Target Version/s: 2.6.0 (was: 2.7.0) Affects Version/s: 2.6.0 Assignee: Yi Liu

[jira] [Resolved] (YARN-2665) Audit warning of registry project

[ https://issues.apache.org/jira/browse/YARN-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-2665. -- Resolution: Duplicate Closing this as a duplicate of YARN-2667, as that already has a patch. Audit

[jira] [Commented] (YARN-2667) Fix the release audit warning caused by hadoop-yarn-registry

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

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169474#comment-14169474 ] zhihai xu commented on YARN-2566: - 1. The two Findbugs warning is not related to my change

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169500#comment-14169500 ] Karthik Kambatla commented on YARN-2566: +1 IOException happen in startLocalizer

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169528#comment-14169528 ] Allen Wittenauer commented on YARN-2495: I don't fully understand your question,

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169530#comment-14169530 ] Karthik Kambatla commented on YARN-2566: Can we file a follow-up JIRA to fix this

[jira] [Commented] (YARN-2651) Spin off the LogRollingInterval from LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169564#comment-14169564 ] Zhijie Shen commented on YARN-2651: --- +1 for the patch. Before commit it, [~xgong], would

[jira] [Updated] (YARN-2651) Spin off the LogRollingInterval from LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2651: -- Hadoop Flags: Reviewed Spin off the LogRollingInterval from LogAggregationContext

[jira] [Updated] (YARN-2651) Spin off the LogRollingInterval from LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2651: Description: Remove per-app rolling interval completely and then have nodemanager wake up every so often and

[jira] [Created] (YARN-2682) WindowsSecureContainerExecutor should not depend on DefaultContainerExecutor#getFirstApplicationDir.

zhihai xu created YARN-2682: --- Summary: WindowsSecureContainerExecutor should not depend on DefaultContainerExecutor#getFirstApplicationDir. Key: YARN-2682 URL: https://issues.apache.org/jira/browse/YARN-2682

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169594#comment-14169594 ] zhihai xu commented on YARN-2566: - [~Karthik Kambatla], Yes, it is a good point. I just

[jira] [Updated] (YARN-2682) WindowsSecureContainerExecutor should not depend on DefaultContainerExecutor#getFirstApplicationDir.

[ https://issues.apache.org/jira/browse/YARN-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2682: Priority: Minor (was: Major) WindowsSecureContainerExecutor should not depend on

[jira] [Updated] (YARN-2651) Spin off the LogRollingInterval from LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2651: -- Description: Remove per-app rolling interval completely and then have nodemanager wake up every so often

[jira] [Commented] (YARN-2651) Spin off the LogRollingInterval from LogAggregationContext

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

[jira] [Updated] (YARN-2679) add container launch prepare time metrics to NM.

[ https://issues.apache.org/jira/browse/YARN-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2679: Attachment: (was: YARN-2679.000.patch) add container launch prepare time metrics to NM.

[jira] [Updated] (YARN-2679) add container launch prepare time metrics to NM.

[ https://issues.apache.org/jira/browse/YARN-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2679: Attachment: YARN-2679.000.patch add container launch prepare time metrics to NM.

[jira] [Commented] (YARN-2377) Localization exception stack traces are not passed as diagnostic info

[ https://issues.apache.org/jira/browse/YARN-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169700#comment-14169700 ] Jason Lowe commented on YARN-2377: -- +1 latest patch lgtm. The audit failure is unrelated,

[jira] [Updated] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-2308: -- Attachment: YARN-2308.1.patch Add explicit logging before exception throw, just in case the exception

[jira] [Created] (YARN-2683) document registry config options

Steve Loughran created YARN-2683: Summary: document registry config options Key: YARN-2683 URL: https://issues.apache.org/jira/browse/YARN-2683 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-2377) Localization exception stack traces are not passed as diagnostic info

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

[jira] [Commented] (YARN-2679) add container launch prepare time metrics to NM.

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

[jira] [Commented] (YARN-2582) Log related CLI and Web UI changes for Aggregated Logs in LRS

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

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

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

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169843#comment-14169843 ] Craig Welch commented on YARN-2308: --- The unit test failure does not appear to be related

[jira] [Commented] (YARN-570) Time strings are formated in different timezone

[ https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169849#comment-14169849 ] Ray Chiang commented on YARN-570: - I've been playing around with this patch some. I'm fine

[jira] [Commented] (YARN-570) Time strings are formated in different timezone

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

[jira] [Commented] (YARN-2656) RM web services authentication filter should add support for proxy user

[ https://issues.apache.org/jira/browse/YARN-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169857#comment-14169857 ] Varun Vasudev commented on YARN-2656: - The latest patch looks good to me. RM web

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169892#comment-14169892 ] Jian He commented on YARN-2308: --- patch looks good to me NPE happened when RM restart after

[jira] [Updated] (YARN-2683) document registry config options

[ https://issues.apache.org/jira/browse/YARN-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2683: - Attachment: YARN-2683-001.patch document registry config options

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169899#comment-14169899 ] Jian He commented on YARN-2308: --- [~lichangleo] , thanks for your previous work ! and thanks

[jira] [Reopened] (YARN-2483) TestAMRestart#testShouldNotCountFailureToMaxAttemptRetry fails due to incorrect AppAttempt state

[ https://issues.apache.org/jira/browse/YARN-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reopened YARN-2483: --- reopen this, as I see the test starts failing again recently..

[jira] [Commented] (YARN-913) Umbrella: Add a way to register long-lived services in a YARN cluster

[ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169908#comment-14169908 ] Steve Loughran commented on YARN-913: - the registry uses curator; we need one that is

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169959#comment-14169959 ] Jian He commented on YARN-2308: --- just realized that we probably should do the same for

[jira] [Created] (YARN-2684) FairScheduler should tolerate queue configuration changes across RM restarts

Karthik Kambatla created YARN-2684: -- Summary: FairScheduler should tolerate queue configuration changes across RM restarts Key: YARN-2684 URL: https://issues.apache.org/jira/browse/YARN-2684

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169969#comment-14169969 ] Karthik Kambatla commented on YARN-2308: Thanks for the nudge, Jian. Filed

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169984#comment-14169984 ] Wangda Tan commented on YARN-2495: -- Hi [~Naganarasimha], First I think need to take care

[jira] [Created] (YARN-2685) Resource on each label not correct when multiple NMs in a same host and some has label some not

Wangda Tan created YARN-2685: Summary: Resource on each label not correct when multiple NMs in a same host and some has label some not Key: YARN-2685 URL: https://issues.apache.org/jira/browse/YARN-2685

[jira] [Updated] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2641: Attachment: YARN-2641.003.patch improve node decommission latency in RM.

[jira] [Updated] (YARN-2685) Resource on each label not correct when multiple NMs in a same host and some has label some not

[ https://issues.apache.org/jira/browse/YARN-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2685: - Attachment: YARN-2685-20141013.1.patch Attached a fix for this, also added a new test to verify when

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

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

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170003#comment-14170003 ] Jian He commented on YARN-2308: --- thanks Karthik. committing this. NPE happened when RM

[jira] [Commented] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170011#comment-14170011 ] zhihai xu commented on YARN-2641: - Hi [~kasha], Yes, they are inherently racy. The user

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170026#comment-14170026 ] Wangda Tan commented on YARN-2314: -- Hi [~jlowe], Looking at this issue recently. I think

[jira] [Updated] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2641: --- Summary: Decommission nodes on -refreshNodes instead of next NM-RM heartbeat (was: improve

[jira] [Commented] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170030#comment-14170030 ] Karthik Kambatla commented on YARN-2641: +1, pending Jenkins. Decommission nodes

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170045#comment-14170045 ] Sangjin Lee commented on YARN-2314: --- We have been running with the proposed patch

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170054#comment-14170054 ] Wangda Tan commented on YARN-2314: -- [~sjlee0], Thanks for your reply, it's very helpful to

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

[ https://issues.apache.org/jira/browse/YARN-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2571: - Attachment: YARN-2571-003.patch patch -003 (against branch-2). Exceptions thrown in the async

[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=14170063#comment-14170063 ] Craig Welch commented on YARN-1680: --- Hi [~airbots], did the newly-discovered concern with

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170082#comment-14170082 ] Jason Lowe commented on YARN-2314: -- The patch effectively restores 0.23 behavior in this

[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=14170083#comment-14170083 ] Chen He commented on YARN-1680: --- Agree with you and [~jlowe]. Maybe post the patch the next

[jira] [Updated] (YARN-2502) Changes in distributed shell to support specify labels

[ https://issues.apache.org/jira/browse/YARN-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2502: - Attachment: YARN-2502-20141013.1.patch Attached a new patch addressed latest comments by [~vinodkv].

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170088#comment-14170088 ] Wangda Tan commented on YARN-2314: -- Thanks [~jlowe]! ContainerManagementProtocolProxy

[jira] [Commented] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

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

[jira] [Commented] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170127#comment-14170127 ] Jian He commented on YARN-2641: --- looks good to me too, thanks Zhihai ! Decommission nodes

[jira] [Commented] (YARN-2685) Resource on each label not correct when multiple NMs in a same host and some has label some not

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

[jira] [Updated] (YARN-2566) DefaultContainerExecutor should pick a working directory randomly

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2566: --- Summary: DefaultContainerExecutor should pick a working directory randomly (was: IOException

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

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-2056: - Attachment: YARN-2056.201410132225.txt [~leftnoteasy], Thanks for all of your help. After looking through

[jira] [Commented] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170149#comment-14170149 ] zhihai xu commented on YARN-2641: - I didn't see the failure(TestAMRestart) in my local

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

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

[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=14170179#comment-14170179 ] Hadoop QA commented on YARN-2571: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170199#comment-14170199 ] Karthik Kambatla commented on YARN-2641: Committing this. Decommission nodes on

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170224#comment-14170224 ] Wangda Tan commented on YARN-2314: -- Discussed with [~vinodkv] offline, summary of what we

[jira] [Commented] (YARN-2566) DefaultContainerExecutor should pick a working directory randomly

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170231#comment-14170231 ] Karthik Kambatla commented on YARN-2566: Committing this..

[jira] [Commented] (YARN-2641) Decommission nodes on -refreshNodes instead of next NM-RM heartbeat

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

[jira] [Commented] (YARN-2566) DefaultContainerExecutor should pick a working directory randomly

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

[jira] [Commented] (YARN-2667) Fix the release audit warning caused by hadoop-yarn-registry

[ https://issues.apache.org/jira/browse/YARN-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170291#comment-14170291 ] Yi Liu commented on YARN-2667: -- Thanks [~jlowe] for review and commit. Fix the release audit

[jira] [Commented] (YARN-2631) Modify DistributedShell to enable LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170328#comment-14170328 ] Xuan Gong commented on YARN-2631: - The purpose for this changes is for testing. But after

[jira] [Resolved] (YARN-2631) Modify DistributedShell to enable LogAggregationContext

[ https://issues.apache.org/jira/browse/YARN-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-2631. - Resolution: Invalid Modify DistributedShell to enable LogAggregationContext

[jira] [Commented] (YARN-2683) document registry config options

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