[jira] [Created] (YARN-1737) Deadlock in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity

zhaoyunjiong created YARN-1737: -- Summary: Deadlock in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity Key: YARN-1737 URL: https://issues.apache.org/jira/browse/YARN-1737 Project: Hadoop

[jira] [Updated] (YARN-1737) Deadlock in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity

[ https://issues.apache.org/jira/browse/YARN-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-1737: --- Attachment: YARN-1737.patch This patch may resolve the problem, I didn't test it yet. Deadlock in

[jira] [Updated] (YARN-1737) Deadlock in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity

[ https://issues.apache.org/jira/browse/YARN-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-1737: --- Attachment: (was: YARN-1737.patch) Deadlock in

[jira] [Updated] (YARN-1737) Deadlock in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity

[ https://issues.apache.org/jira/browse/YARN-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-1737: --- Attachment: YARN-1737.patch Deadlock in

[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=13906861#comment-13906861 ] Hudson commented on YARN-1666: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #487 (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=13906866#comment-13906866 ] Hudson commented on YARN-1718: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #487 (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=13906860#comment-13906860 ] Hudson commented on YARN-1171: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #487 (See

[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=13906868#comment-13906868 ] Hudson commented on YARN-1479: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #487 (See

[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=13906870#comment-13906870 ] Hudson commented on YARN-713: - SUCCESS: Integrated in Hadoop-Yarn-trunk #487 (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=13906966#comment-13906966 ] Hudson commented on YARN-1666: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1679 (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=13906965#comment-13906965 ] Hudson commented on YARN-1171: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1679 (See

[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=13906975#comment-13906975 ] Hudson commented on YARN-713: - SUCCESS: Integrated in Hadoop-Hdfs-trunk #1679 (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=13906971#comment-13906971 ] Hudson commented on YARN-1718: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1679 (See

[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=13906973#comment-13906973 ] Hudson commented on YARN-1479: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1679 (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=13907016#comment-13907016 ] Hudson commented on YARN-1171: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1704 (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=13907017#comment-13907017 ] Hudson commented on YARN-1666: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1704 (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=13907022#comment-13907022 ] Hudson commented on YARN-1718: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1704 (See

[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=13907024#comment-13907024 ] Hudson commented on YARN-1479: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1704 (See

[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=13907026#comment-13907026 ] Hudson commented on YARN-713: - SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1704 (See

[jira] [Created] (YARN-1739) Add a log message like encrypted shuffle is ON in nodemanager logs

Yesha Vora created YARN-1739: Summary: Add a log message like encrypted shuffle is ON in nodemanager logs Key: YARN-1739 URL: https://issues.apache.org/jira/browse/YARN-1739 Project: Hadoop YARN

[jira] [Resolved] (YARN-1675) Application does not change to RUNNING after being scheduled

[ https://issues.apache.org/jira/browse/YARN-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1675. --- Resolution: Duplicate Really closing as duplicate of YARN-1689. Application

[jira] [Created] (YARN-1740) Redirection from AM-URL is broken with HTTPS_ONLY policy

Yesha Vora created YARN-1740: Summary: Redirection from AM-URL is broken with HTTPS_ONLY policy Key: YARN-1740 URL: https://issues.apache.org/jira/browse/YARN-1740 Project: Hadoop YARN Issue

[jira] [Assigned] (YARN-1739) Add a log message like encrypted shuffle is ON in nodemanager logs

[ https://issues.apache.org/jira/browse/YARN-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-1739: - Assignee: Jian He Add a log message like encrypted shuffle is ON in nodemanager logs

[jira] [Assigned] (YARN-1740) Redirection from AM-URL is broken with HTTPS_ONLY policy

[ https://issues.apache.org/jira/browse/YARN-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-1740: - Assignee: Jian He Redirection from AM-URL is broken with HTTPS_ONLY policy

[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.6.patch throw out ServiceFailedException for all the refresh*s calls in

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13907408#comment-13907408 ] Naren Koneru commented on YARN-1736: The change was made to an internal private

[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 ] Karthik Kambatla reassigned YARN-1736: -- Assignee: Naren Koneru (was: Sandy Ryza) In Fair Scheduler,

[jira] [Resolved] (YARN-1422) RM CapacityScheduler can deadlock when getQueueUserAclInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1422. --- Resolution: Duplicate This is a duplicate of YARN-1398 which existed before

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13907426#comment-13907426 ] Karthik Kambatla commented on YARN-1736: LGTM. +1. In Fair Scheduler,

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

[jira] [Updated] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

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

[jira] [Updated] (YARN-1736) FS: AppSchedulable.assignContainer's priority argument is redundant

[ https://issues.apache.org/jira/browse/YARN-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1736: --- Summary: FS: AppSchedulable.assignContainer's priority argument is redundant (was: In Fair

[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=13907437#comment-13907437 ] Zhijie Shen commented on YARN-1071: --- The approach should fix the problem here. Some minor

[jira] [Commented] (YARN-1736) FS: AppSchedulable.assignContainer's priority argument is redundant

[ https://issues.apache.org/jira/browse/YARN-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907443#comment-13907443 ] Karthik Kambatla commented on YARN-1736: Thanks Naren. Committed to trunk and

[jira] [Commented] (YARN-1736) FS: AppSchedulable.assignContainer's priority argument is redundant

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

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

[jira] [Created] (YARN-1741) XInclude support broken for YARN ResourceManager

Eric Sirianni created YARN-1741: --- Summary: XInclude support broken for YARN ResourceManager Key: YARN-1741 URL: https://issues.apache.org/jira/browse/YARN-1741 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-1470) Add audience annotation to MiniYARNCluster

[ https://issues.apache.org/jira/browse/YARN-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1470: --- Assignee: Anubhav Dhoot Add audience annotation to MiniYARNCluster

[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=13907654#comment-13907654 ] Jian He commented on YARN-1071: --- Thanks zhijie for the review ! bq.

[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.4.patch ResourceManager's decommissioned and lost node count is 0 after restart

[jira] [Updated] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

[ https://issues.apache.org/jira/browse/YARN-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1398: -- Attachment: YARN-1398-20140220.txt Here's a patch that reverts the behavior

[jira] [Updated] (YARN-1739) Add a log message like encrypted shuffle is ON in nodemanager logs

[ https://issues.apache.org/jira/browse/YARN-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1739: -- Attachment: YARN-1739.1.patch Added the log message to indicate encrypted shuffle on or not , which is good

[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=13907666#comment-13907666 ] Xuan Gong commented on YARN-1410: - bq. What are the pros and cons of duplicate checking

[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=13907669#comment-13907669 ] Bikas Saha commented on YARN-1410: -- That is interesting because NameNode uses the same RPC

[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=13907673#comment-13907673 ] Zhijie Shen commented on YARN-1071: --- bq. That's hadoop-common code, we should probably

[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=13907694#comment-13907694 ] Bikas Saha commented on YARN-1410: -- I am repeatedly asking for this because its a problem

[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.5.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=13907707#comment-13907707 ] Jian He commented on YARN-1071: --- bq. NodesListManager#disableHostsFileReader? Right, updated

[jira] [Commented] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

: YARN-1398-20140220.txt getQueueInfo in parentQueue will call child.getQueueInfo(). This will try acquire the leaf queue lock over parent queue lock. Now at same time if a completedContainer call comes and acquired LeafQueue lock and it will wait for ParentQueue's completedConatiner call

[jira] [Commented] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.0 Reporter: Sunil G Assignee: Vinod Kumar Vavilapalli Priority: Blocker Attachments: YARN-1398-20140220.txt getQueueInfo in parentQueue

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907726#comment-13907726 ] Vinod Kumar Vavilapalli commented on YARN-1741: --- [~sirianni], will you be

[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=13907760#comment-13907760 ] Suresh Srinivas commented on YARN-1410: --- [~xgong], ping me if you need any help.

[jira] [Commented] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12630180/YARN-1398-20140220.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear

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

[jira] [Created] (YARN-1742) Fix javadoc of parameter DEFAULT_NM_MIN_HEALTHY_DISKS_FRACTION

Akira AJISAKA created YARN-1742: --- Summary: Fix javadoc of parameter DEFAULT_NM_MIN_HEALTHY_DISKS_FRACTION Key: YARN-1742 URL: https://issues.apache.org/jira/browse/YARN-1742 Project: Hadoop YARN

[jira] [Updated] (YARN-1742) Fix javadoc of parameter DEFAULT_NM_MIN_HEALTHY_DISKS_FRACTION

[ https://issues.apache.org/jira/browse/YARN-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-1742: Attachment: YARN-1742.patch Attaching a patch. Fix javadoc of parameter

[jira] [Commented] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12630180/YARN-1398-20140220.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear

[jira] [Commented] (YARN-1742) Fix javadoc of parameter DEFAULT_NM_MIN_HEALTHY_DISKS_FRACTION

[ https://issues.apache.org/jira/browse/YARN-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907844#comment-13907844 ] Hadoop QA commented on YARN-1742: - {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=13907857#comment-13907857 ] Zhijie Shen commented on YARN-1071: --- I thought about another scenario: a. host1 and

[jira] [Assigned] (YARN-1429) YARN_CLASSPATH is referenced in yarn command comments but doesn't do anything

[ https://issues.apache.org/jira/browse/YARN-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho reassigned YARN-1429: Assignee: Jarek Jarcec Cecho YARN_CLASSPATH is referenced in yarn command comments

[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.6.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=13907871#comment-13907871 ] Jian He commented on YARN-1071: --- bq. So this scenario should still be covered with this

[jira] [Commented] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

Attachments: YARN-1398-20140220.txt getQueueInfo in parentQueue will call child.getQueueInfo(). This will try acquire the leaf queue lock over parent queue lock. Now at same time if a completedContainer call comes and acquired LeafQueue lock and it will wait for ParentQueue's

[jira] [Commented] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call

Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.0 Reporter: Sunil G Assignee: Vinod Kumar Vavilapalli Priority: Blocker Fix For: 2.4.0 Attachments: YARN-1398-20140220.txt getQueueInfo in parentQueue

[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 monitoring graphs the AvailableMB of each queue regularly spikes between the AllocatedMB and

[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 monitoring graphs the AvailableMB of each queue regularly spikes between the AllocatedMB and

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

[jira] [Updated] (YARN-1735) For FairScheduler 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: -- Summary: For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB (was: AvailableMB in

[jira] [Moved] (YARN-1743) Decorate event transitions and the event-types with their behaviour

[ https://issues.apache.org/jira/browse/YARN-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3164 to YARN-1743: -- Component/s: (was: mrv2) Affects

[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=13907937#comment-13907937 ] Xuan Gong commented on YARN-1410: - Thanks for the suggestions. But this proposal seems have

[jira] [Commented] (YARN-1687) Refactoring timeline classes to remove app related words

[ https://issues.apache.org/jira/browse/YARN-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907948#comment-13907948 ] Zhijie Shen commented on YARN-1687: --- Let's do refactoring after YARN-1732 Refactoring

[jira] [Created] (YARN-1744) Renaming applicationhistoryservice module

Zhijie Shen created YARN-1744: - Summary: Renaming applicationhistoryservice module Key: YARN-1744 URL: https://issues.apache.org/jira/browse/YARN-1744 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-1744) Renaming applicationhistoryservice module

[ https://issues.apache.org/jira/browse/YARN-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1744: -- Issue Type: Sub-task (was: Bug) Parent: YARN-321 Renaming applicationhistoryservice module

[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=13907956#comment-13907956 ] Zhijie Shen commented on YARN-1071: --- +1. The patch looks good to me. Vinod, do you want

[jira] [Updated] (YARN-1744) Renaming applicationhistoryservice module

[ https://issues.apache.org/jira/browse/YARN-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1744: -- Description: When we started with the feature, the module only contains the source code of generic

[jira] [Updated] (YARN-1687) Refactoring timeline classes to remove app related words

[ https://issues.apache.org/jira/browse/YARN-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1687: -- Attachment: YARN-1687+YARN-1732.1.patch Submit a combined patch of YARN-1687 and YARN-1732 for jenkins

[jira] [Updated] (YARN-1687) Refactoring timeline classes to remove app related words

[ https://issues.apache.org/jira/browse/YARN-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1687: -- Attachment: YARN-1687.2.patch Create a new patch that rebases against the latest trunk, and on top 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=13908029#comment-13908029 ] Zhijie Shen commented on YARN-1071: --- Will commit the patch ResourceManager's

[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=13908055#comment-13908055 ] Hudson commented on YARN-1071: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5203 (See

[jira] [Commented] (YARN-1687) Refactoring timeline classes to remove app related words

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