Speaker office hours will take place on the Confluent community slack on:
- February 7 at 8am PST
- February 21 at 8am PST
- Februar 21 at 4pm PST
If you're looking for advice on your abstract, this is the place to be. See you there!
https://t.co/O9FqVoK7Cj
@MichaelDrogalis@rmoff@apachekafka Many people asks about this issue for legitimate usecases but it is hard. And there is no right way yet even agreed on. BTW another option is to setup a metrics server's client to read the metrics programmatically. Bit ugly but it will be related to your topic/brokers.
@MichaelDrogalis@rmoff@apachekafka The problem with this approach is that it doesn't tell you if the brokers that hold your partitions or down or busy but it tells you the broker that received this request is down or slow. This is a problem with large clusters especially if your topic has small no. partitions.
@MichaelDrogalis@rmoff@apachekafka This is hard problem in Kafka. One workaround for the consumer is to use ‘consumer.listTopics’ in a retry and if you failed few times you can assume the broker is either slow or down.Or use AdminClient to describe your topic which your client should be authorised to do anyway.
We are now hiring across different positions at Pinterest.
* US-based applicants who are authorized to work only. *
I am happy to refer friends, friends of friends and/or exceptional talents.
DM me with your CV if interested.
https://t.co/a9norJvjFZ