[jira] [Updated] (YARN-463) Show explicitly excluded nodes on the UI

2015-07-15 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-463: -- Attachment: YARN-463.1.patch Update patch fix test failures. Show explicitly excluded nodes on the UI

[jira] [Updated] (YARN-463) Show explicitly excluded nodes on the UI

2015-07-14 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-463: -- Attachment: YARN-463.patch Screen Shot 2015-07-14 at 1.25.46 PM.png This patch add

[jira] [Reopened] (YARN-463) Show explicitly excluded nodes on the UI

2015-07-14 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong reopened YARN-463: --- Assignee: zhaoyunjiong Currently hosts already in yarn.resourcemanager.nodes.exclude-path when

[jira] [Updated] (YARN-3423) RM HA setup, Cluster tab links populated with AM hostname instead of RM

2015-03-31 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-3423: --- Attachment: YARN-3423.patch When yarn.resourcemanager.webapp.https.address=0.0.0.0:8090

[jira] [Updated] (YARN-3423) RM HA setup, Cluster tab links populated with AM hostname instead of RM

2015-03-31 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-3423: --- Attachment: YARN-3423.patch Update patch, the previous patch is not right. Below are configs from our

[jira] [Updated] (YARN-3423) RM HA setup, Cluster tab links populated with AM hostname instead of RM

2015-03-31 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-3423: --- Attachment: (was: YARN-3423.patch) RM HA setup, Cluster tab links populated with AM hostname

[jira] [Resolved] (YARN-1888) Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port

2014-04-01 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong resolved YARN-1888. Resolution: Not a Problem Thank you Jason Lowe and Karthik Kambatla for your time. Now I agree

[jira] [Reopened] (YARN-1888) Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port

2014-03-29 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong reopened YARN-1888: The problem here is our cluster use port 0, but when restart NodeManager, the Lost Nodes became

[jira] [Created] (YARN-1888) Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port

2014-03-28 Thread zhaoyunjiong (JIRA)
zhaoyunjiong created YARN-1888: -- Summary: Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port Key: YARN-1888 URL: https://issues.apache.org/jira/browse/YARN-1888

[jira] [Updated] (YARN-1888) Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port

2014-03-28 Thread zhaoyunjiong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong updated YARN-1888: --- Attachment: YARN-1888.patch When RMNodeImpl do DeactivateNodeTransition, check whether there is

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

2014-02-20 Thread zhaoyunjiong (JIRA)
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

2014-02-20 Thread zhaoyunjiong (JIRA)
[ 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

2014-02-20 Thread zhaoyunjiong (JIRA)
[ 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

2014-02-20 Thread zhaoyunjiong (JIRA)
[ 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