You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/07/11 20:56:05 UTC

[jira] [Commented] (SAMZA-329) AM should read checkpoints and provide them to containers

    [ https://issues.apache.org/jira/browse/SAMZA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059199#comment-14059199 ] 

Chris Riccomini commented on SAMZA-329:
---------------------------------------

Not sure how this ticket would be affected by a ConfigLog (as discussed in SAMZA-123). If we end up using the ConfigLog as a way to send signals to containers, then the containers will still need to read the log. That said, having the AM read the config log and pass in static stuff to the containers at start time doesn't prohibit the containers from also reading the log, thought it might not provide any gain.

> AM should read checkpoints and provide them to containers
> ---------------------------------------------------------
>
>                 Key: SAMZA-329
>                 URL: https://issues.apache.org/jira/browse/SAMZA-329
>             Project: Samza
>          Issue Type: Improvement
>          Components: kafka
>            Reporter: Jakob Homan
>
> Currently each container reads its checkpoint partition to find the latest offsets.  Post SAMZA-123, the checkpoints are written into a single-partition topic that each container reads through, discarding those checkpoints for which it does not have SSPs.  It would be better if the AM were to read the checkpoint once and pass the offset to the container as part of the input stream definition.



--
This message was sent by Atlassian JIRA
(v6.2#6252)