You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/05/18 20:08:04 UTC

[jira] [Resolved] (KAFKA-5033) Reconsider default retries for idempotent producer

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

Jason Gustafson resolved KAFKA-5033.
------------------------------------
    Resolution: Fixed

Issue resolved by pull request 3091
[https://github.com/apache/kafka/pull/3091]

> Reconsider default retries for idempotent producer
> --------------------------------------------------
>
>                 Key: KAFKA-5033
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5033
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Ismael Juma
>            Assignee: Apurva Mehta
>            Priority: Blocker
>              Labels: exactly-once
>             Fix For: 0.11.0.0
>
>
> We currently set the default to 3 if idempotence is enabled. There was a brief discussion in the PR, but it would be good to explain this choice in more detail. Namely, what cases are we trying to cover with this number and have we considered the fact that with the default retry backoff of 100ms, 3 retries are used pretty quickly.
> Is there a downside in using a larger retry count?
> cc [~apurva]



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