[jira] [Commented] (YARN-1428) RM cannot write the final state of RMApp/RMAppAttempt to the application history store in the transition to the final state

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

[jira] [Commented] (YARN-1590) _HOST doesn't expand properly for RM, NM, ProxyServer and JHS

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

[jira] [Commented] (YARN-1724) Race condition in Fair Scheduler when continuous scheduling is turned on

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

[jira] [Commented] (YARN-1721) When moving app between queues in Fair Scheduler, grab lock on FSSchedulerApp

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

[jira] [Commented] (YARN-1171) Add default queue properties to Fair Scheduler documentation

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

[jira] [Commented] (YARN-1071) ResourceManager's decommissioned and lost node count is 0 after restart

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

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

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

[jira] [Commented] (YARN-1724) Race condition in Fair Scheduler when continuous scheduling is turned on

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

[jira] [Commented] (YARN-1721) When moving app between queues in Fair Scheduler, grab lock on FSSchedulerApp

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

[jira] [Commented] (YARN-1590) _HOST doesn't expand properly for RM, NM, ProxyServer and JHS

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

[jira] [Commented] (YARN-1428) RM cannot write the final state of RMApp/RMAppAttempt to the application history store in the transition to the final state

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

[jira] [Commented] (YARN-1724) Race condition in Fair Scheduler when continuous scheduling is turned on

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

[jira] [Commented] (YARN-1721) When moving app between queues in Fair Scheduler, grab lock on FSSchedulerApp

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

[jira] [Commented] (YARN-1590) _HOST doesn't expand properly for RM, NM, ProxyServer and JHS

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

[jira] [Commented] (YARN-1428) RM cannot write the final state of RMApp/RMAppAttempt to the application history store in the transition to the final state

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

[jira] [Resolved] (YARN-1694) RM is shutting down when an NM is added to cluster without updating the hostname in /etc/hosts

[ https://issues.apache.org/jira/browse/YARN-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1694. --- Resolution: Duplicate Yes it is. RM is shutting down when an NM is added to

[jira] [Commented] (YARN-1479) Invalid NaN values in Hadoop REST API JSON response

[ https://issues.apache.org/jira/browse/YARN-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905740#comment-13905740 ] Jonathan Eagles commented on YARN-1479: --- +1. Making a minor tweak to the sleep time

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905754#comment-13905754 ] Vinod Kumar Vavilapalli commented on YARN-1666: --- +1, looks good. Checking

[jira] [Commented] (YARN-1479) Invalid NaN values in Hadoop REST API JSON response

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

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

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

[jira] [Updated] (YARN-1071) ResourceManager's decommissioned and lost node count is 0 after restart

[ https://issues.apache.org/jira/browse/YARN-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1071: -- Attachment: YARN-1071.2.patch ResourceManager's decommissioned and lost node count is 0 after restart

[jira] [Commented] (YARN-1071) ResourceManager's decommissioned and lost node count is 0 after restart

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

[jira] [Commented] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905799#comment-13905799 ] Mit Desai commented on YARN-1281: - Is this failure just related to the test or is there

[jira] [Updated] (YARN-1071) ResourceManager's decommissioned and lost node count is 0 after restart

[ https://issues.apache.org/jira/browse/YARN-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1071: -- Attachment: YARN-1071.3.patch ResourceManager's decommissioned and lost node count is 0 after restart

[jira] [Updated] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1297: --- Description: I ran the Fair Scheduler's core scheduling loop through a profiler tool and

[jira] [Commented] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905816#comment-13905816 ] Karthik Kambatla commented on YARN-1297: +1 Miscellaneous Fair Scheduler speedups

[jira] [Commented] (YARN-1428) RM cannot write the final state of RMApp/RMAppAttempt to the application history store in the transition to the final state

[ https://issues.apache.org/jira/browse/YARN-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905814#comment-13905814 ] Jian He commented on YARN-1428: --- Committed to branch-2.4 also. RM cannot write the final

[jira] [Commented] (YARN-1678) Fair scheduler gabs incessantly about reservations

[ https://issues.apache.org/jira/browse/YARN-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905803#comment-13905803 ] Karthik Kambatla commented on YARN-1678: Thanks Sandy. Looks good to me except for

[jira] [Commented] (YARN-1171) Add default queue properties to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905831#comment-13905831 ] Sandy Ryza commented on YARN-1171: -- +1, LGTM. Thanks Naren! Add default queue

[jira] [Commented] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905833#comment-13905833 ] Karthik Kambatla commented on YARN-1281: I believe it is just related to the test,

[jira] [Commented] (YARN-1071) ResourceManager's decommissioned and lost node count is 0 after restart

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

[jira] [Created] (YARN-1735) AvailableMB in QueueMetrics is the same as AllocateMB

Siqi Li created YARN-1735: - Summary: AvailableMB in QueueMetrics is the same as AllocateMB Key: YARN-1735 URL: https://issues.apache.org/jira/browse/YARN-1735 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-1735) AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Component/s: scheduler resourcemanager AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Updated] (YARN-1735) AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Description: in Viz graphs the AvailableMB of each queue regularly spikes between the AllocatedMB and the

[jira] [Updated] (YARN-1735) AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Description: in Viz graphs the AvailableMB of each queue regularly spikes between the AllocatedMB and the

[jira] [Updated] (YARN-1735) AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Description: in Viz graphs the AvailableMB of each queue regularly spikes between the AllocatedMB and the

[jira] [Commented] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906020#comment-13906020 ] Mit Desai commented on YARN-1281: - I had tried it on my machine and it was passing too.

[jira] [Resolved] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai resolved YARN-1281. - Resolution: Cannot Reproduce Target Version/s: (was: ) This JIRA has been open for a long

[jira] [Commented] (YARN-1171) Add default queue properties to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906100#comment-13906100 ] Naren Koneru commented on YARN-1171: Changed the issue to reflect the current state of

[jira] [Updated] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-713: - Attachment: YARN-713.5.patch ResourceManager can exit unexpectedly if DNS is unavailable

[jira] [Updated] (YARN-1171) Add default queue properties to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1171: - Assignee: Naren Koneru (was: Karthik Kambatla) Add default queue properties to Fair Scheduler

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906102#comment-13906102 ] Jian He commented on YARN-713: -- bq. May be resend the container-allocated event in a thread

[jira] [Updated] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-713: - Attachment: YARN-713.6.patch New patch with minor more fix ResourceManager can exit unexpectedly if DNS is

[jira] [Commented] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906125#comment-13906125 ] Karthik Kambatla commented on YARN-1281: I actually see this failing in our nightly

[jira] [Updated] (YARN-1171) Add default queue properties to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1171: - Fix Version/s: (was: 2.5.0) 2.4.0 Add default queue properties to Fair Scheduler

[jira] [Commented] (YARN-1171) Add default queue properties to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906128#comment-13906128 ] Sandy Ryza commented on YARN-1171: -- and branch-2.4 Add default queue properties to Fair

[jira] [Created] (YARN-1736) In Fair Scheduler, AppSchedulable.assignContainer Priority argument is redundant with ResourceRequest

Sandy Ryza created YARN-1736: Summary: In Fair Scheduler, AppSchedulable.assignContainer Priority argument is redundant with ResourceRequest Key: YARN-1736 URL: https://issues.apache.org/jira/browse/YARN-1736

[jira] [Updated] (YARN-1678) Fair scheduler gabs incessantly about reservations

[ https://issues.apache.org/jira/browse/YARN-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1678: - Attachment: YARN-1678-1.patch Fair scheduler gabs incessantly about reservations

[jira] [Commented] (YARN-986) YARN should use cluster-id as token service address

[ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906154#comment-13906154 ] Vinod Kumar Vavilapalli commented on YARN-986: -- Any update? Can we take it over

[jira] [Commented] (YARN-1678) Fair scheduler gabs incessantly about reservations

[ https://issues.apache.org/jira/browse/YARN-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906202#comment-13906202 ] Karthik Kambatla commented on YARN-1678: +1, pending Jenkins. Thanks Sandy. Fair

[jira] [Commented] (YARN-986) YARN should use cluster-id as token service address

[ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906203#comment-13906203 ] Karthik Kambatla commented on YARN-986: --- Was pulled away for something else. I have

[jira] [Assigned] (YARN-1736) In Fair Scheduler, AppSchedulable.assignContainer Priority argument is redundant with ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naren Koneru reassigned YARN-1736: -- Assignee: Naren Koneru In Fair Scheduler, AppSchedulable.assignContainer Priority argument is

[jira] [Updated] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1734: Attachment: YARN-1734.2.patch RM should get the updated Configurations when it transits from Standby to

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906224#comment-13906224 ] Xuan Gong commented on YARN-1734: - After YARN-1 is checked in, we do have InputStream

[jira] [Reopened] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai reopened YARN-1281: - I see Karthik. Reopening it TestZKRMStateStoreZKClientConnections fails intermittently

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906287#comment-13906287 ] Vinod Kumar Vavilapalli commented on YARN-713: -- +1, looks good. Checking this

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906304#comment-13906304 ] Arpit Agarwal commented on YARN-713: Is this error in branch-2.4 related? {code} WARN:

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

[jira] [Commented] (YARN-1171) Add default queue properties to Fair Scheduler documentation

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

[jira] [Commented] (YARN-1718) Fix a couple isTerminals in Fair Scheduler queue placement rules

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Updated] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

[ https://issues.apache.org/jira/browse/YARN-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1588: -- Attachment: YARN-1588.3.patch Rebind NM tokens for previous attempt's running containers to the new attempt

[jira] [Commented] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

[ https://issues.apache.org/jira/browse/YARN-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906361#comment-13906361 ] Jian He commented on YARN-1588: --- Fixed the naming getContainersFromPreviousAttempt to be

[jira] [Updated] (YARN-1731) ResourceManager should record killed ApplicationMasters for History

[ https://issues.apache.org/jira/browse/YARN-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-1731: Attachment: YARN-1731.patch Updated patch ResourceManager should record killed ApplicationMasters

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906425#comment-13906425 ] Vinod Kumar Vavilapalli commented on YARN-713: -- Yes, I did see the issue on

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906445#comment-13906445 ] Xuan Gong commented on YARN-1734: - bq. Why is refreshAdminAcls() required to be done when

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906452#comment-13906452 ] Vinod Kumar Vavilapalli commented on YARN-713: -- Done. Compiled branches

[jira] [Commented] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

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

[jira] [Updated] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1734: Attachment: YARN-1734.3.patch RM should get the updated Configurations when it transits from Standby to

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906468#comment-13906468 ] Arpit Agarwal commented on YARN-713: Thanks Vinod! ResourceManager can exit

[jira] [Updated] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1734: Attachment: YARN-1734.4.patch RM should get the updated Configurations when it transits from Standby to

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906526#comment-13906526 ] Xuan Gong commented on YARN-1734: - throw out the IOException instead of just log

[jira] [Updated] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cindy Li updated YARN-1525: --- Attachment: YARN1525.patch Vinod, made changes according to your comment. resetting RM_ID allows me to find

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Updated] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking

[ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1363: -- Attachment: YARN-1363.6.patch Create a new patch: 1. Update against the latest trunk 2. Refactor some

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Updated] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1734: Attachment: YARN-1734.5.patch RM should get the updated Configurations when it transits from Standby to

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906592#comment-13906592 ] Xuan Gong commented on YARN-1734: - should do the same (throw out the IOException instead of

[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Updated] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1410: Attachment: YARN-1410.4.patch Handle client failover during 2 step client API's like app submission

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906632#comment-13906632 ] Xuan Gong commented on YARN-1410: - Offline discussed with [~vinodkv]. We still use the

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906646#comment-13906646 ] Wei Yan commented on YARN-1726: --- Thanks, [~vinodkv]. Sure, I'll update a testcase.

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

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

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906670#comment-13906670 ] Xuan Gong commented on YARN-1410: - test case failure is not related Handle client

[jira] [Commented] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking

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

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906703#comment-13906703 ] Bikas Saha commented on YARN-1410: -- What are the pros and cons of duplicate checking