[
https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-2308:
--
Attachment: YARN-2308.1.patch
Add explicit logging before exception throw, just in case the exception
[
https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Welch updated YARN-2308:
--
Attachment: YARN-2308.0.patch
Here's a patch which does what I believe the consensus was - detects the
[
https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chang li updated YARN-2308:
---
Attachment: jira2308.patch
updated patch according to Wangda's advice
NPE happened when RM restart after
[
https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chang li updated YARN-2308:
---
Attachment: jira2308.patch
patch updated according to Wangda's suggestion
NPE happened when RM restart
[
https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chang li updated YARN-2308:
---
Attachment: jira2308.patch
NPE happened when RM restart after CapacityScheduler queue configuration
[
https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chang li updated YARN-2308:
---
Attachment: jira2308.patch
NPE happened when RM restart after CapacityScheduler queue configuration
