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 2015/02/26 23:09:06 UTC

[jira] [Updated] (SAMZA-579) KafkaSystemConsumer drops SSPs on failure

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

Chris Riccomini updated SAMZA-579:
----------------------------------
    Attachment: SAMZA-579-0.patch

Attaching a patch that fixes the problem. Running with the SAMZA-394 integration test shows the containers no longer wedge.

> KafkaSystemConsumer drops SSPs on failure
> -----------------------------------------
>
>                 Key: SAMZA-579
>                 URL: https://issues.apache.org/jira/browse/SAMZA-579
>             Project: Samza
>          Issue Type: Bug
>          Components: kafka
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>             Fix For: 0.9.0
>
>         Attachments: SAMZA-579-0.patch
>
>
> While running SAMZA-394, I discovered a bug in KafkaSystemConsumer that causes it to stop consuming under failure scenarios. This does not cause data loss, but can wedge a container until it's restarted.
> The trigger appears to be when a BrokerProxy fetches from a broker that's still coming up, and hasn't yet claimed ownership for a TopicAndPartition. When the fetch fails, the BrokerProxy abdicate()s the TopicAndPartition, and KafkaSystemConsumer tries to refresh to get the leader. If there is no leader, the KafkaSystemConsumer drops the SSP. This happens in KafkaSystemConsumer.refreshBrokers.



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