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

Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2017/05/09 00:49:04 UTC

[jira] [Resolved] (SAMZA-1147) ZkJobCoordinator does not honor the interface contract of JobCoordinator

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

Navina Ramesh resolved SAMZA-1147.
----------------------------------
    Resolution: Duplicate

Duplicate - All issues were addressed in SAMZA-1212

> ZkJobCoordinator does not honor the interface contract of JobCoordinator
> ------------------------------------------------------------------------
>
>                 Key: SAMZA-1147
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1147
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>            Priority: Critical
>             Fix For: 0.13.0
>
>
> There is a mismatch in how StandaloneJobCoordinator and ZkJobCoordinator handle the start/stop/awaitStart semantics of JobCoordinator. 
> This impacts the StreamProcessor API behavior as well since the guarantees on the semantics of start / stop of the processors are broken in different runtime environments. This is weird and we need to revisit the how the components interact - StreamProcessor, JobCoordinator and SamzaContainer. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)