[KAFKA-5796] Understand performance implications of acks=all and potential ways to reduce it

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Apurva Mehta
• Reporter: Apurva Mehta
• Created: 26/Aug/17 03:10
• Updated: 16/Sep/17 00:58

Description

To get exactly once semantics, we need acks=all. However, we know that there is a latency and throughput impact with acks=all when compared with acks=1.

The impact is quantified here:
https://cwiki.apache.org/confluence/display/KAFKA/An+analysis+of+the+impact+of+max.in.flight.requests.per.connection+and+acks+on+Producer+performance

However, we can't explain some of that data. Nor do we know the causes for some of the degradation. We would like to understand the performance of acks=all at the very minimum before making it the default producer setting.