[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-1857:
--
Attachment: YARN-1857.7.patch
I see it now - uploading newer patch with simplified final headroom
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-1857:
--
Attachment: YARN-1857.5.patch
Updating to current trunk on new(er) repo
CapacityScheduler headroom
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-1857:
--
Attachment: YARN-1857.4.patch
[~john.jian.fang] I've attached a .4 patch with the additional checks you
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-1857:
--
Attachment: YARN-1857.3.patch
re attaching patch to get the javac warnings
CapacityScheduler headroom
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-1857:
--
Attachment: YARN-1857.2.patch
I went ahead and put in a comment wrt a headroom value in the test and
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen He updated YARN-1857:
--
Target Version/s: 2.6.0 (was: 2.4.1)
CapacityScheduler headroom doesn't account for other AM's running
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-1857:
--
Attachment: YARN-1857.1.patch
Just updating to a patch which applies against current trunk, otherwise
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen He updated YARN-1857:
--
Attachment: YARN-1857.patch
trigger QA
CapacityScheduler headroom doesn't account for other AM's running
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated YARN-1857:
--
Priority: Critical (was: Major)
CapacityScheduler headroom doesn't account for other AM's
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated YARN-1857:
--
Target Version/s: 2.4.1 (was: 2.4.0)
CapacityScheduler headroom doesn't account for other
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen He updated YARN-1857:
--
Attachment: YARN-1857.patch
CapacityScheduler headroom doesn't account for other AM's running
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen He updated YARN-1857:
--
Attachment: YARN-1857.patch
CapacityScheduler headroom doesn't account for other AM's running
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Graves updated YARN-1857:
Description:
Its possible to get an application to hang forever (or a long time) in a
cluster with
[
https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-1857:
--
Issue Type: Sub-task (was: Bug)
Parent: YARN-1198
CapacityScheduler
14 matches
Mail list logo