[
https://issues.apache.org/jira/browse/SAMZA-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647244#comment-14647244
]
Richard Lee commented on SAMZA-563:
-----------------------------------
You need to enable RM restart phase 2 to see the problem w/ Samza. In
particular, the addition of the 'epoch' information seems to be what screws up
the AM.
See
https://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/ResourceManagerRestart.html
"ContainerId string format is changed if RM restarts with work-preserving
recovery enabled. It used to be such format:
Container_{clusterTimestamp}_{appId}_{attemptId}_{containerId}, e.g.
Container_1410901177871_0001_01_000005.
It is now changed to:
Container_e{epoch}_{clusterTimestamp}_{appId}_{attemptId}_{containerId}, e.g.
Container_e17_1410901177871_0001_01_000005."
> Upgrade Samza to YARN 2.6.0
> ---------------------------
>
> Key: SAMZA-563
> URL: https://issues.apache.org/jira/browse/SAMZA-563
> Project: Samza
> Issue Type: Bug
> Components: yarn
> Affects Versions: 0.9.0
> Reporter: Chris Riccomini
> Assignee: Aleksandar Pejakovic
> Attachments: HELLO-SAMZA-563.0.patch, SAMZA-563.0.patch,
> SAMZA-563.2.patch
>
>
> Samza is currently running on YARN 2.4.0. We should upgrade it to YARN 2.6.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
