[jira] [Updated] (SAMZA-1146) TaskCallbackManager commit fix.

["Xinyu Liu (JIRA)" <ji...@apache.org>]

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

Xinyu Liu updated SAMZA-1146:
-----------------------------
    Affects Version/s: 0.12.0
        Fix Version/s: 0.13.0

> TaskCallbackManager commit fix.
> -------------------------------
>
>                 Key: SAMZA-1146
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1146
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Shanthoosh Venkataraman
>            Assignee: Shanthoosh Venkataraman
>             Fix For: 0.13.0
>
>
> Each task callback in samza belongs to different SystemStreamPartition. When multiple callbacks in contagious order are available for commit, callback with highest sequence number is chosen for commit. This will prevent checkpointing of completed callbacks that has commit request and doesn't have highest sequence number. Upon task restart this will lead to duplicate reprocessing of already processed messages (since completed callbacks for some SystemStreamPartition's aren't committed earlier). 
> Expected behavior is to commit all completed callbacks that has commit request associated with it.



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