g
> > >> kafka.server:name=LeaderCount,type=ReplicaManager which tells me when
> > the
> > >> broker is actually operational and serving data.
> > >>
> > >> On Mon, Aug 17, 2020 at 3:29 PM Dhirendra Singh <
> dhirendr...@gmail.com>
&
leader for partitions it owned before restart,
> but
> >> that's not the case.
> >>
> >> In the end I've settled for checking
> >> kafka.server:name=LeaderCount,type=ReplicaManager which tells me when
> the
> >> broker is actually operational an
restart, but
>> that's not the case.
>>
>> In the end I've settled for checking
>> kafka.server:name=LeaderCount,type=ReplicaManager which tells me when the
>> broker is actually operational and serving data.
>>
>> On Mon, Aug 17, 2020 at
> On Mon, Aug 17, 2020 at 3:29 PM Dhirendra Singh
> wrote:
>
> > I have a question regarding Kafka BrokerState Metric value 3. According
> to
> > the documentation value 3 means running state.
> > What does this running state mean for the broker? Does it mean data of
> all
s actually operational and serving data.
On Mon, Aug 17, 2020 at 3:29 PM Dhirendra Singh
wrote:
> I have a question regarding Kafka BrokerState Metric value 3. According to
> the documentation value 3 means running state.
> What does this running state mean for the broker? Does
I have a question regarding Kafka BrokerState Metric value 3. According to
the documentation value 3 means running state.
What does this running state mean for the broker? Does it mean data of all
partitions on this broker is in sync ?
Is it safe to assume that when broker transition to state 3
