[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792121#comment-13792121
]
Jian He commented on YARN-1058:
---
Believe we have fixed this, close it.
Recovery issues on
[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792179#comment-13792179
]
Karthik Kambatla commented on YARN-1058:
I have also noticed that this was fixed in
[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792190#comment-13792190
]
Jian He commented on YARN-1058:
---
YARN-1116 fixed the AMRMToken part , MAPREDUCE-5476 fixed
[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738934#comment-13738934
]
Karthik Kambatla commented on YARN-1058:
I was expecting the first one, and Bikas
[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739013#comment-13739013
]
Bikas Saha commented on YARN-1058:
--
It could be that history service was not properly
[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737021#comment-13737021
]
Bikas Saha commented on YARN-1058:
--
The first one is expected because the RM is currently
[
https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737100#comment-13737100
]
Jian He commented on YARN-1058:
---
As Bikas said, the first exception is expected because
