You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2017/04/18 22:24:42 UTC

[jira] [Updated] (SAMZA-750) Run YARN RM Recovery test to uncover any potential issues with SamzaAppMaster

     [ https://issues.apache.org/jira/browse/SAMZA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yi Pan (Data Infrastructure) updated SAMZA-750:
-----------------------------------------------
    Fix Version/s: 0.12.0

> 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: Shanthoosh Venkataraman
>             Fix For: 0.12.0
>
>
> 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.15#6346)