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:50:04 UTC

[jira] [Updated] (SAMZA-330) Checkpoint log and state log should resize partition count upward if necessary at job start

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

Chris Riccomini updated SAMZA-330:
----------------------------------

          Component/s: kv
                       container
    Affects Version/s: 0.7.0

> Checkpoint log and state log should resize partition count upward if necessary at job start
> -------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-330
>                 URL: https://issues.apache.org/jira/browse/SAMZA-330
>             Project: Samza
>          Issue Type: Improvement
>          Components: container, kv
>    Affects Versions: 0.7.0
>            Reporter: Jakob Homan
>
> Currently if a the checkpoint log or state log partition count increases on job restart due to the inclusion of new streams with a higher partition count, the corresponding Kafka topics are increased to accommodate this change.  In the case of the the checkpoint log, we will get a job failure at startup.  We should compare the current partition size with the required and size upward if necessary at job start.  



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