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

Posted to commits@samza.apache.org by "Martin Kleppmann (JIRA)" <ji...@apache.org> on 2014/03/05 16:15:45 UTC

[jira] [Commented] (SAMZA-108) Samza task hangs on startup with new state store

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

Martin Kleppmann commented on SAMZA-108:
----------------------------------------

In my tests, it looks like this is the same underlying problem as SAMZA-169, as the issue no longer occurs for me. [~alanwli] would you mind applying the patches for SAMZA-168 and SAMZA-169 to trunk, and checking if that also fixes the problem for you?

> Samza task hangs on startup with new state store
> ------------------------------------------------
>
>                 Key: SAMZA-108
>                 URL: https://issues.apache.org/jira/browse/SAMZA-108
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Alan Li
>            Assignee: Martin Kleppmann
>
> When a new state store is added, the Samza task will hang on startup with messages like:
> 2013-12-17 16:37:10 KafkaSystemConsumer [WARN] No such topic-partition: [your-state-store,0], dropping.
> It seems that there are issues with initializing the kafka changelog topic the first time. Restarting the samza task again is the workaround for this problem.



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