Kafka Consumer does not receive data when one of the brokers is down

后端 未结 2 828
情深已故
情深已故 2021-01-16 03:12

Kafka Quickstart
Using Kafka v2.1.0 on RHEL v6.9

Consumer fails to receive data when one of the Kafka brokers is down.

Steps performed:
1. Start

相关标签:
2条回答
  • 2021-01-16 03:52

    If the offsets topic is unavailable, you cannot consume.

    Look at the server.properties file for these, and see the comment above, and increase accordingly (only applies if topic doesn't already exist)

    # The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
    # For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.
    offsets.topic.replication.factor=1
    transaction.state.log.replication.factor=1
    

    According to your previous question, looks like it only has one replica

    See how you can increase replication factor for an existing topic

    0 讨论(0)
  • 2021-01-16 04:18

    In initial versions of Kafka, offset was being managed at zookeeper, but Kafka has continuously evolved over the time introducing lot of new features. Now Kafka manages the offset in a topic __consumer_offsets.

    You can think of a scenario where you created a topic with a replication factor of 1. In case the broker goes down the data is only on that Kafka node which is down. So you can't get this data. Same analogy applies to __consumer_offsets topic.

    You need to revisit the server.properties in order to get features you are expecting. But in case you still wanna consume the messages from the replica partition, you may need to re-start the console consumer with --from-beginning true

    0 讨论(0)
提交回复
热议问题