10

I have 3 brokers running with broker id s 0 1 and 2. The Consumer (Java Client) picks up broker 0 as group coordinator and starts to consume messages correctly. But when the broker 0 which is the group coordinator is down, the consumer does not do anything and stalls on the poll() method. The process resumes only when that broker 0 is up and running.

How to handle this scenario of group co-ordinator change in the Java client?

I get this error when group coordinator dies:

16/09/22 17:42:45 INFO internals.AbstractCoordinator: Discovered coordinator datascience1.sv2.trulia.com:9092 (id: 2147483647 rack: null) for group group2.
16/09/22 17:42:45 INFO internals.AbstractCoordinator: (Re-)joining group group2
16/09/22 17:42:45 INFO internals.AbstractCoordinator: Marking the coordinator datascience1.sv2.trulia.com:9092 (id: 2147483647 rack: null) dead for group group2
Pang
  • 9,564
  • 146
  • 81
  • 122

1 Answers1

0

See this answer: https://stackoverflow.com/a/50954843/7321097 and https://stackoverflow.com/a/50595475/7321097

The isue is in the offsets.topic.replication.factor & replication.factor configs.

Chaouki Dhib
  • 389
  • 4
  • 17