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/19 16:35:46 UTC

[jira] [Closed] (SAMZA-168) Getting Kafka system metadata should back off on retry

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

Martin Kleppmann closed SAMZA-168.
----------------------------------


> Getting Kafka system metadata should back off on retry
> ------------------------------------------------------
>
>                 Key: SAMZA-168
>                 URL: https://issues.apache.org/jira/browse/SAMZA-168
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Martin Kleppmann
>            Assignee: Martin Kleppmann
>             Fix For: 0.7.0
>
>         Attachments: SAMZA-168.patch
>
>
> If an exception occurs in KafkaSystemAdmin.getSystemStreamMetadata (eg because the broker returns an error for the partitions metadata request), we currently retry in a tight loop. This puts unnecessary load on Kafka, and especially risks hammering Zookeeper.
> There should be an exponential back-off in the retry loop.



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