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

Posted to commits@samza.apache.org by "Naveen (JIRA)" <ji...@apache.org> on 2015/04/02 00:55:54 UTC

[jira] [Updated] (SAMZA-465) Use coordinator stream and eliminate CheckpointManager

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

Naveen updated SAMZA-465:
-------------------------
    Attachment: SAMZA-465.patch

> Use coordinator stream and eliminate CheckpointManager
> ------------------------------------------------------
>
>                 Key: SAMZA-465
>                 URL: https://issues.apache.org/jira/browse/SAMZA-465
>             Project: Samza
>          Issue Type: Sub-task
>          Components: container, kafka
>    Affects Versions: 0.10.0
>            Reporter: Chris Riccomini
>            Assignee: Naveen
>             Fix For: 0.10.0
>
>         Attachments: SAMZA-465.patch
>
>
> SAMZA-448 introduced a coordinator stream into Samza, but still kept CheckpointManagers. This means that master currently has two streams, which is totally unnecessary. We should eliminate the CheckpointManager, and use the coordinator stream instead.
> This work will involve modifying the JobCoordinator to continue reading messages from the coordinator stream even after it starts up. This is required because a container may fail and restart. When it does so, the offset that it receives from the JobCoordinator (via the HTTP JSON server) must be up to date.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)