Brilliant, thanks for that Matthias :)
On Tue, 18 Aug. 2020, 3:07 am Matthias J. Sax, wrote:
> Your understanding is correct.
>
> On 8/16/20 10:25 PM, Liam Clarke-Hutchinson wrote:
> > Kia ora koutou katoa,
> >
> > Just double checking my understanding - the RecordMetadata returned by a
> >
Timothy,
please follow the instructions from the webpage to unsubscribe:
https://kafka.apache.org/contact
The mailing list is self-service.
-Matthias
On 8/17/20 8:39 AM, Gaudet, Timothy wrote:
> Can you please remove me from the mailing list?
>
> Timothy Gaudet
> Linux Engineer
> General
Can you please remove me from the mailing list?
Timothy Gaudet
Linux Engineer
General Dynamics Information Technology _Intelligence Solututions Div. (ISD)
US BICES-X and Intelligence Programs
Tampa, FL.
813-826-0110
0015002659 BICES
timothy.gau...@gdit.com
timothy.d.gaudet@socom.mil
Hello Sanjay,
I've just added you to the contributor list in Jira, so you
should be able to assign tickets now.
Thanks for your interest in the project!
-John
On Sun, 2020-08-16 at 21:27 -0500, Sanjay Y R wrote:
> Hello,
>
> I am Sanjay. I am a Kafka user intending to contribute to Kafka Open
Your understanding is correct.
On 8/16/20 10:25 PM, Liam Clarke-Hutchinson wrote:
> Kia ora koutou katoa,
>
> Just double checking my understanding - the RecordMetadata returned by a
> producer send returns an offset for the record - is it the actual offset of
> the record on the partition, or
Hello,
I am Sanjay. I am a Kafka user intending to contribute to Kafka Open Source
codebase. Right now, I am going through the Kafka documentation and looking
to fix any issues I find. Could you please add me to the Kafka
contributors list so that I can assign the issue to myself? My details are
I tried using this metric for determining when the broker is back in the
cluster and became the 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
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
