[
https://issues.apache.org/jira/browse/SAMZA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406860#comment-15406860
]
Jake Maes commented on SAMZA-750:
---------------------------------
We're going to take a stab at supporting work-preserving-recovery in the next
major release:
Initial Plan:
1. Set up a test cluster with
yarn.resourcemanager.work-preserving-recovery.enabled ([~jonbringhurst] FYI)
2. Try upgrading the samza hadoop dependency and see if that fixes the issue.
If so, we'll support 2.7 as the minimum version in the next major release.
3. Try running with the updated samza dependencies on an older 2.6 hadoop
cluster. Ideally it will still work, so users can safely upgrade samza with no
change to their clusters.
> Run YARN RM Recovery test to uncover any potential issues with SamzaAppMaster
> -----------------------------------------------------------------------------
>
> Key: SAMZA-750
> URL: https://issues.apache.org/jira/browse/SAMZA-750
> Project: Samza
> Issue Type: Test
> Components: yarn
> Affects Versions: 0.10.0
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Jake Maes
>
> Currently, there is no tests toward YARN RM Recovery support in Samza.
> As pointed out by [~llamahunter], there is likely some issue in containerID
> versioning in SamzaAppMaster to handle RM Recovery case. There might be more
> issues.
> This JIRA is to track the effort to uncover the issues related to YARN RM
> Recovery feature. The outcome expected is:
> 1) Some test suite that runs Samza jobs in YARN with RM Recovery
> 2) A list of issues discovered. Each issue may result in a separate JIRA to
> be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
