[
https://issues.apache.org/jira/browse/KAFKA-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta resolved KAFKA-5640.
---------------------------------
Resolution: Duplicate
This is a dup of https://issues.apache.org/jira/browse/KAFKA-5796
> Look into making acks=all the default setting
> ---------------------------------------------
>
> Key: KAFKA-5640
> URL: https://issues.apache.org/jira/browse/KAFKA-5640
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Apurva Mehta
> Assignee: Apurva Mehta
> Fix For: 1.0.0
>
>
> KAFKA-5494 proposed dropping the requirement for
> {{max.inflight.requests.per.connection=1}} for the idempotent producer.
> That is a stepping stone to enabling the idempotent producer by default
> without sacrificing performance.
> A further step would be making {{acks=all}} the default setting as well.
> Then, with {{enable.idempotence=true}},
> {{max.inflight.requests.per.connection=5}}, {{acks=all}},
> {{retries=MAX_INT}}, we would have exactly once semantics with strong
> durability guarantees.
> This particular ticket is about investigating the performance degradation
> caused by {{acks=all}}. How much does throughput degrade? If it is
> significant, are there low hanging fruit in terms of code or config changes
> which would allow us to bridge most of the gap?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
