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

Posted to commits@samza.apache.org by "Hai Lu (Jira)" <ji...@apache.org> on 2019/11/07 00:06:03 UTC

[jira] [Updated] (SAMZA-1531) Support run.id in standalone for batch processing

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

Hai Lu updated SAMZA-1531:
--------------------------
    Fix Version/s: 1.3

> Support run.id in standalone for batch processing
> -------------------------------------------------
>
>                 Key: SAMZA-1531
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1531
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Xinyu Liu
>            Assignee: Shanthoosh Venkataraman
>            Priority: Major
>             Fix For: 1.3
>
>          Time Spent: 26h 20m
>  Remaining Estimate: 0h
>
> Similar to Yarn, we need to generate a unique run.id per job run in standalone. Right now the lock is acquired after the plan is generated, then the streams are created. Instead, we need to generate the id first, acquiring the lock based on this id, then generate the plan as well as the streams.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)