[jira] [Updated] (YARN-2494) [YARN-796] Node label manager API and storage implementations

[ https://issues.apache.org/jira/browse/YARN-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2494: - Attachment: YARN-2494.patch [YARN-796] Node label manager API and storage implementations

[jira] [Commented] (YARN-2494) [YARN-796] Node label manager API and storage implementations

[ https://issues.apache.org/jira/browse/YARN-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136872#comment-14136872 ] Wangda Tan commented on YARN-2494: -- Hi [~cwelch], Thanks for your comments, bq. the only

[jira] [Updated] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2558: - Attachment: YARN-2558.2.patch [~jianhe], thanks for your suggestion and review. Updated to add

[jira] [Commented] (YARN-2496) [YARN-796] Changes for capacity scheduler to support allocate resource respect labels

[ https://issues.apache.org/jira/browse/YARN-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136878#comment-14136878 ] Wangda Tan commented on YARN-2496: -- Hi [~cwelch], I'm not sure quite understand about

[jira] [Commented] (YARN-2494) [YARN-796] Node label manager API and storage implementations

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

[jira] [Commented] (YARN-2505) [YARN-796] Support get/add/remove/change labels in RM REST API

[ https://issues.apache.org/jira/browse/YARN-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136891#comment-14136891 ] Wangda Tan commented on YARN-2505: -- Hi Craig, I've reviewed this patch, some comments: 1)

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

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

[jira] [Updated] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2561: - Attachment: YARN-2561-v2.patch Update the patch to fix the test failure. MR job client cannot reconnect

[jira] [Updated] (YARN-2498) [YARN-796] Respect labels in preemption policy of capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2498: - Attachment: yarn-2498-implementation-notes.pdf [YARN-796] Respect labels in preemption policy of capacity

[jira] [Commented] (YARN-2498) [YARN-796] Respect labels in preemption policy of capacity scheduler

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

[jira] [Commented] (YARN-2498) [YARN-796] Respect labels in preemption policy of capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136987#comment-14136987 ] Wangda Tan commented on YARN-2498: -- Attached implementation notes, [~curino], [~sunilg],

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136993#comment-14136993 ] Steve Loughran commented on YARN-2562: -- +1 for text making it clear what the values

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136998#comment-14136998 ] Hadoop QA commented on YARN-2561: - {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=14137013#comment-14137013 ] Sunil G commented on YARN-2308: --- +1 for this approach. I also feel that returning application

[jira] [Commented] (YARN-1250) Generic history service should support application-acls

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

[jira] [Commented] (YARN-2531) CGroups - Admins should be allowed to enforce strict cpu limits

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

[jira] [Commented] (YARN-2557) Add a parameter attempt_Failures_Validity_Interval in DistributedShell

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

[jira] [Created] (YARN-2565) ResourceManager is fails to start when GenericHistoryService is enabled in secure mode without doing manual kinit as yarn

Karam Singh created YARN-2565: - Summary: ResourceManager is fails to start when GenericHistoryService is enabled in secure mode without doing manual kinit as yarn Key: YARN-2565 URL:

[jira] [Commented] (YARN-2565) ResourceManager is fails to start when GenericHistoryService is enabled in secure mode without doing manual kinit as yarn

[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137204#comment-14137204 ] Karam Singh commented on YARN-2565: --- Observed that RM fails to start in Secure mode when

[jira] [Commented] (YARN-1250) Generic history service should support application-acls

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

[jira] [Commented] (YARN-2557) Add a parameter attempt_Failures_Validity_Interval in DistributedShell

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

[jira] [Commented] (YARN-2531) CGroups - Admins should be allowed to enforce strict cpu limits

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

[jira] [Commented] (YARN-2531) CGroups - Admins should be allowed to enforce strict cpu limits

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

[jira] [Commented] (YARN-1250) Generic history service should support application-acls

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

[jira] [Commented] (YARN-2557) Add a parameter attempt_Failures_Validity_Interval in DistributedShell

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

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137385#comment-14137385 ] Jason Lowe commented on YARN-2561: -- Thanks for the patch, Junping! I'm not sure it's best

[jira] [Commented] (YARN-2527) NPE in ApplicationACLsManager

[ https://issues.apache.org/jira/browse/YARN-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137431#comment-14137431 ] Benoy Antony commented on YARN-2527: [~zjshen], any comments ? Since the ACLS are

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137496#comment-14137496 ] Maysam Yabandeh commented on YARN-1963: --- I was wondering what is the long-term plan

[jira] [Updated] (YARN-2554) Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the HTTP policy

[ https://issues.apache.org/jira/browse/YARN-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron updated YARN-2554: - Attachment: YARN-2554.1.patch Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the

[jira] [Commented] (YARN-2554) Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the HTTP policy

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

[jira] [Commented] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137564#comment-14137564 ] Sunil G commented on YARN-1963: --- HI [~maysamyabandeh], We are bringing up a design doc for

[jira] [Updated] (YARN-2554) Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the HTTP policy

[ https://issues.apache.org/jira/browse/YARN-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron updated YARN-2554: - Attachment: YARN-2554.2.patch Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the

[jira] [Updated] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2561: - Attachment: YARN-2561-v3.patch MR job client cannot reconnect to AM after NM restart.

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137590#comment-14137590 ] Junping Du commented on YARN-2561: -- Thanks [~jlowe] for the comments! Yes. Checking

[jira] [Assigned] (YARN-2565) ResourceManager is fails to start when GenericHistoryService is enabled in secure mode without doing manual kinit as yarn

[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-2565: - Assignee: Zhijie Shen ResourceManager is fails to start when GenericHistoryService is enabled in

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

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

[jira] [Commented] (YARN-2554) Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the HTTP policy

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

[jira] [Updated] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2561: - Attachment: YARN-2561-v4.patch Fix the compile issues in v3. MR job client cannot reconnect to AM after

[jira] [Commented] (YARN-2559) ResourceManager sometime become un-responsive due to NPE in SystemMetricsPublisher

[ https://issues.apache.org/jira/browse/YARN-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137636#comment-14137636 ] Jian He commented on YARN-2559: --- To be consistent with the FinalApplicationStatus exposed on

[jira] [Assigned] (YARN-2563) On secure clusters call to timeline server fails with authentication errors when running a job via oozie

[ https://issues.apache.org/jira/browse/YARN-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-2563: - Assignee: Zhijie Shen On secure clusters call to timeline server fails with authentication

[jira] [Commented] (YARN-2446) Using TimelineNamespace to shield the entities of a user

[ https://issues.apache.org/jira/browse/YARN-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137637#comment-14137637 ] Li Lu commented on YARN-2446: - Hi [~zjshen], yes the latest patch looks good to me. Still,

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137644#comment-14137644 ] Vinod Kumar Vavilapalli commented on YARN-2001: --- This looks almost close

[jira] [Commented] (YARN-2468) Log handling for LRS

[ https://issues.apache.org/jira/browse/YARN-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137661#comment-14137661 ] Xuan Gong commented on YARN-2468: - bq. If LogContext is not specified, we're running into

[jira] [Updated] (YARN-2468) Log handling for LRS

[ https://issues.apache.org/jira/browse/YARN-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2468: Attachment: YARN-2468.5.patch Log handling for LRS Key: YARN-2468

[jira] [Commented] (YARN-1779) Handle AMRMTokens across RM failover

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

[jira] [Updated] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2001: -- Attachment: YARN-2001.5.patch Fixed logging to add the wait msg. Threshold for RM to accept requests from AM

[jira] [Commented] (YARN-1779) Handle AMRMTokens across RM failover

[ https://issues.apache.org/jira/browse/YARN-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137685#comment-14137685 ] Xuan Gong commented on YARN-1779: - +1 LGTM Handle AMRMTokens across RM failover

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

[ https://issues.apache.org/jira/browse/YARN-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-1453: --- Attachment: YARN-1453-02.patch Rebased. It doesn't fix all the javadoc errors, but it at

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137696#comment-14137696 ] Jian He commented on YARN-2558: --- the test looks good me, thanks Tsuyoshi ! Updating

[jira] [Commented] (YARN-2179) Initial cache manager structure and context

[ https://issues.apache.org/jira/browse/YARN-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137725#comment-14137725 ] Karthik Kambatla commented on YARN-2179: Review comments: # Rename

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

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

[jira] [Commented] (YARN-2468) Log handling for LRS

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

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

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

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137757#comment-14137757 ] Jason Lowe commented on YARN-2558: -- bq. Jason Lowe, without changing

[jira] [Updated] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2562: - Attachment: YARN-2562.1.patch Thanks for your comment, Steve. Attaching a first patch to change

[jira] [Updated] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2558: - Attachment: YARN-2558.3.patch Thanks for your review, Jian and Jason! Updated: * Removed

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

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

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

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

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137863#comment-14137863 ] Junping Du commented on YARN-2561: -- This test failure looks like a random failure and

[jira] [Commented] (YARN-2080) Admission Control: Integrate Reservation subsystem with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137881#comment-14137881 ] Vinod Kumar Vavilapalli commented on YARN-2080: --- This looks good, +1. Let's

[jira] [Commented] (YARN-1492) truly shared cache for jars (jobjar/libjar)

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137895#comment-14137895 ] Chris Trezzo commented on YARN-1492: [~kasha], [~vinodkv] and I had a conversation

[jira] [Updated] (YARN-2559) ResourceManager sometime become un-responsive due to NPE in SystemMetricsPublisher

[ https://issues.apache.org/jira/browse/YARN-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2559: -- Attachment: YARN-2559.2.patch bq. To be consistent with the FinalApplicationStatus exposed on RM web UI

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

[ https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137903#comment-14137903 ] Varun Vasudev commented on YARN-2190: - [~chuanliu] thanks for the patch! Some questions

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

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

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

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

[jira] [Updated] (YARN-668) TokenIdentifier serialization should consider Unknown fields

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

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137907#comment-14137907 ] Vinod Kumar Vavilapalli commented on YARN-2558: --- bq. Yes, this should be fine

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

[ https://issues.apache.org/jira/browse/YARN-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137908#comment-14137908 ] Junping Du commented on YARN-2561: -- Also, try this patch in a real cluster which works

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137912#comment-14137912 ] Vinod Kumar Vavilapalli commented on YARN-668: -- I think [~sseth]'s solution in

[jira] [Updated] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2001: -- Attachment: YARN-2001.5.patch Test passes locally, re-submit the same patch Threshold for RM to accept

[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=14137937#comment-14137937 ] chang li commented on YARN-2308: thanks for the collective thought about this and all

[jira] [Commented] (YARN-2179) Initial cache manager structure and context

[ https://issues.apache.org/jira/browse/YARN-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137944#comment-14137944 ] Chris Trezzo commented on YARN-2179: [~kasha] a couple of comments: bq. 5.

[jira] [Updated] (YARN-2468) Log handling for LRS

[ https://issues.apache.org/jira/browse/YARN-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2468: Attachment: YARN-2468.5.1.patch Log handling for LRS Key: YARN-2468

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137952#comment-14137952 ] Junping Du commented on YARN-668: - bq. I think Siddharth Seth's solution in the description

[jira] [Updated] (YARN-913) 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:all-tabpanel ] Steve Loughran updated YARN-913: Attachment: YARN-913-003.patch assuming this patch builds (it does appear to locally), this patch #

[jira] [Commented] (YARN-2561) MR job client cannot reconnect to AM after NM restart.

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

[jira] [Updated] (YARN-1779) Handle AMRMTokens across RM failover

[ https://issues.apache.org/jira/browse/YARN-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1779: -- Attachment: YARN-1779.6.patch Thanks Vinod for reviewing. Reverted unnecessary changes. Also changed

[jira] [Commented] (YARN-913) 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=14137997#comment-14137997 ] Hadoop QA commented on YARN-913: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137999#comment-14137999 ] Tsuyoshi OZAWA commented on YARN-668: - +1(non-binding) for making TokenIdentifier

[jira] [Commented] (YARN-2559) ResourceManager sometime become un-responsive due to NPE in SystemMetricsPublisher

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

[jira] [Commented] (YARN-2179) Initial cache manager structure and context

[ https://issues.apache.org/jira/browse/YARN-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138021#comment-14138021 ] Karthik Kambatla commented on YARN-2179: bq. One approach would be to move the

[jira] [Updated] (YARN-2468) Log handling for LRS

[ https://issues.apache.org/jira/browse/YARN-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2468: Attachment: YARN-2468.5.1.patch Log handling for LRS Key: YARN-2468

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

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

[jira] [Commented] (YARN-1779) Handle AMRMTokens across RM failover

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

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138083#comment-14138083 ] Jian He commented on YARN-1372: --- We can probably do this: - Transfer both

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138093#comment-14138093 ] Jian He commented on YARN-2558: --- Committing this, thanks [~jlowe], [~vinodkv] for the

[jira] [Commented] (YARN-2563) On secure clusters call to timeline server fails with authentication errors when running a job via oozie

[ https://issues.apache.org/jira/browse/YARN-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138107#comment-14138107 ] Zhijie Shen commented on YARN-2563: --- When submitting an app in a secure mode, YarnClient

[jira] [Commented] (YARN-2468) Log handling for LRS

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

[jira] [Updated] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2001: -- Attachment: YARN-2001.5.patch Trying the same patch again. no failures actually found in the jenkins console

[jira] [Commented] (YARN-2559) ResourceManager sometime become un-responsive due to NPE in SystemMetricsPublisher

[ https://issues.apache.org/jira/browse/YARN-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138162#comment-14138162 ] Jian He commented on YARN-2559: --- looks good overall, We may just call

[jira] [Updated] (YARN-2563) On secure clusters call to timeline server fails with authentication errors when running a job via oozie

[ https://issues.apache.org/jira/browse/YARN-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2563: -- Attachment: YARN-2563.1.patch Create a patch to fix the aforementioned bug. On secure clusters call to

[jira] [Commented] (YARN-2565) ResourceManager is fails to start when GenericHistoryService is enabled in secure mode without doing manual kinit as yarn

[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138184#comment-14138184 ] Zhijie Shen commented on YARN-2565: --- [~karams], I think you've neglected mentioning the

[jira] [Updated] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore

[ https://issues.apache.org/jira/browse/YARN-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2565: -- Summary: RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting

[jira] [Updated] (YARN-2559) ResourceManager sometime become un-responsive due to NPE in SystemMetricsPublisher

[ https://issues.apache.org/jira/browse/YARN-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2559: -- Attachment: YARN-2559.3.patch Update the patch accordingly ResourceManager sometime become

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

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

[jira] [Commented] (YARN-2565) RM shouldn't use the old RMApplicationHistoryWriter unless explicitly setting FileSystemApplicationHistoryStore

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

[jira] [Commented] (YARN-2080) Admission Control: Integrate Reservation subsystem with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138234#comment-14138234 ] Karthik Kambatla commented on YARN-2080: Looks mostly good. Nits: There are some

[jira] [Updated] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2139: -- Attachment: Disk_IO_Scheduling_Design_2.pdf Update a new design doc including spindle-locality information.

[jira] [Commented] (YARN-2563) On secure clusters call to timeline server fails with authentication errors when running a job via oozie

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

[jira] [Commented] (YARN-2558) Updating ContainerTokenIdentifier#read/write to use ContainerId#getContainerId

[ https://issues.apache.org/jira/browse/YARN-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14138272#comment-14138272 ] Tsuyoshi OZAWA commented on YARN-2558: -- Thanks Jason, Vinod, and Jian for the comments

  1   2   >