kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronald van de Kuil (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-5997) acks=all does not seem to be honoured
Date Sat, 30 Sep 2017 07:15:00 GMT
Ronald van de Kuil created KAFKA-5997:

             Summary: acks=all does not seem to be honoured
                 Key: KAFKA-5997
                 URL: https://issues.apache.org/jira/browse/KAFKA-5997
             Project: Kafka
          Issue Type: Bug
          Components: producer 
    Affects Versions:
            Reporter: Ronald van de Kuil

I have a 3 node Kafka cluster. I made a topic with 1 partition with a replication factor of

The replicas landed on broker 1 and 3. 

When I stopped the leader I still could produce on it. Also, I saw the consumer consume it.

I produced with acks=all:

[main] INFO org.apache.kafka.clients.producer.ProducerConfig - ProducerConfig values: 
	acks = all

The documentations says says about acc=all:
"This means the leader will wait for the full set of in-sync replicas to acknowledge the record."

The producer api returns the offset which is present in the Metadatarecord.

I would have expected that producer could not publish because only 1 replica is in sync.

This is the output of the topic state:

Topic:topic1    PartitionCount:1        ReplicationFactor:2     Configs:
        Topic: topic1   Partition: 0    Leader: 1       Replicas: 1,3   Isr: 1

I am wondering whether or not this is a bug in the current version of the API or whether the
documentation (or my understanding) is eligible for an update? I expect the former.

If there is anything that I can do, please let me know.

This message was sent by Atlassian JIRA

View raw message