A company is setting up a log ingestion use case where they will consume logs from numerous systems. The company wants to tune Kafka for the utmost throughput. In this scenario, what acknowledgment…

The correct answer is A. acks=0. acks=0 provides the highest throughput because the producer does not wait for any acknowledgment from the broker. This minimizes latency and maximizes performance. However, it comes at the cost of no durability guarantees -- messages may be lost if the broker fails before…

Ensuring Data Reliability and Durability

Question

A company is setting up a log ingestion use case where they will consume logs from numerous systems. The company wants to tune Kafka for the utmost throughput. In this scenario, what acknowledgment setting makes the most sense?

Options

Aacks=0
Backs=1
Cacks=all
Dacks=underfined

How the community answered

(63 responses)

A
70% (44)
B
8% (5)
C
17% (11)
D
5% (3)

Explanation

acks=0 provides the highest throughput because the producer does not wait for any acknowledgment from the broker. This minimizes latency and maximizes performance. However, it comes at the cost of no durability guarantees -- messages may be lost if the broker fails before writing them. This setting is suitable when throughput is critical and occasional data loss is acceptable, such as in some log ingestion use cases where logs are also stored

Topics

#acks=0#producer throughput#acknowledgment#log ingestion

Community Discussion

No community discussion yet for this question.

Full CCAAK Practice