Re: Kafka 2.1.0 JMX mbean broken ?

2018-12-14 Thread Raghav
I got it to work. I fired up a console and then saw what beans are registered there and then queries using the code. It works then. But the apiVersion is different and how do we know what apiVersion a producer is using ? Our dashboards cannot have a-priori knowledge of the version numbers, and wil

Re: Kafka 2.1.0 JMX mbean broken ?

2018-12-14 Thread Raghav
Is this a test case for this commit: https://github.com/apache/kafka/pull/4506 ? I have tried using all possible cases but cannot get it to work. I cannot get it to work using mbean reader via JMX. Can any one please help? Or atleast confirm that it is broken. Thanks R On Fri, Dec 14, 2018 at 6:

Re: MAX_TASK_IDLE_MS_CONFIG not working?

2018-12-14 Thread Guozhang Wang
Hello Dmitry, There are generally speaking two sources of out-of-ordering data from the viewpoint of Kafka Streams, and you can find them on the web docs here: https://kafka.apache.org/21/documentation/streams/core-concepts#streams_out_of_ordering As Matthias mentioned, if the source topics alrea

Re: Kafka 2.1.0 JMX mbean broken ?

2018-12-14 Thread Raghav
Thanks Ismael. How to query it in 2.1 ? I tried all possible ways including using version, but I am still getting the same exception message. Thanks for your help. On Thu, Dec 13, 2018 at 7:19 PM Ismael Juma wrote: > The metric was changed to include the API version. I believe this was in > the

Re: MAX_TASK_IDLE_MS_CONFIG not working?

2018-12-14 Thread Matthias J. Sax
If you have out-of-order data, there is no guarantee that the current record has larger timestamp than previous record. Data is still processed in offset order. Also, you use selectKey() and groupByKey() thus triggering a repartioning that may introduce out-of-order data downstream even if all you