Re: Kafka 2.1.0 JMX mbean broken ?

Hi Raghav, As you know, KIP-372 added "version" tag to RequestsPerSec metric to monitor requests for each version. As mentioned in the KIP, to get total count per request (across all versions), we need to aggregate over all versions. You may need to automate this by fetching all metrics using wild

Re: Kafka 2.1.0 JMX mbean broken ?

Hello Allen, Ted, Mani, Gwen, James https://www.mail-archive.com/dev@kafka.apache.org/msg86226.html I read this email thread and I see that you guys were split in going ahead with this change. This has broken our dashboard in 2.1 Kafka, which is ok as long as we know how to fix it. Can you pleas

Re: [VOTE] 2.2.0 RC1 [CANCELED]

A blocker was found: https://issues.apache.org/jira/browse/KAFKA-8069 I am canceling this VOTE in favor of a new RC. -Matthias On 3/7/19 10:13 AM, Jonathan Santilli wrote: > Hello Matthias, I have run the tests without issue. > Also, I have performed the quick start successfully, thanks for the

question about kafka topic

Hi, I have a question about kafka topic, recently we face kafka client sending message to kafka topic issue, got error about offset, and client can not send message to kafka cluster. My question is, since we configure kafka servers to one cluster, when cluster get message, will it try it best t

Re: KTable.suppress(Suppressed.untilWindowCloses) does not suppress some non-final results when the kafka streams process is restarted

Sure John, I will document it. Thanks a lot for your reply. -- Jonathan On Tue, Mar 5, 2019 at 7:38 PM John Roesler wrote: > Hi Jonathan, > > Just a quick update: I have not been able to reproduce the duplicates issue > with the 2.2 RC, even with a topology very similar to the one you includ

reseting dirty offset

Hello all, This morning I got the following error: [2019-03-08 09:43:03,066] WARN Resetting first dirty offset to log start offset 1 since the checkpointed offset 0 is invalid. (kafka.log.LogCleanerManager$) If I correctly understand, the log cleaner try to