Hi Amitav, Brokers only write to controller log when they're the cluster controller. So if you wanted to see what the cluster controller was doing at a given point in time, then yep, you'd want to aggregate all controller.log files to handle controller changes. Typically controller status is very stable, it only really changes if you're restarting a broker or it fails.
You can tell which broker is controller by looking at the JMX exposed metric kafka.controller:type=KafkaController,name=ActiveControllerCount, it'll be 1 if a broker is the controller, 0 otherwise (and if that metric ever adds up to more than 1 across your cluster, you've got problems). > To follow the leader of any given partition, do we need to correlate across controller logs of all brokers ? What do you mean by follow the leader? Cheers, Liam Clarke-Hutchinson On Wed, 20 May 2020, 7:04 am Amitav Mohanty, <amitavmohant...@gmail.com> wrote: > Hi > > I am trying to understand the right way of viewing controller > logs. As the controller logs are written in each broker, do we need > to see all of them to know the state of the cluster at any given > point in time ? To follow the leader of any given partition, do we need to > correlate > across controller logs of all brokers ? > > Regards, > Amitav >
