Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #189

See Changes: -- [...truncated 417461 lines...] org.apache.kafka.streams.integration.StoreQueryIntegrationTest >

Re: Re: Re: [DISCUSS] KIP-972: Add the metric of the current running version of kafka

Thank you for your answer, Mickael. If set the value of gauge to a constant value of 1, adding that tag key is "version" and value is the version value of the obtained string type, does this solve the problem? We can get the version by tag in prometheus. best, hudeqi Mickael Maison

Re: Re: [VOTE] KIP-965: Support disaster recovery between clusters by MirrorMaker

Thank you for your thoughtfulness, greg. 1. This configuration only relevant to the MirrorSourceConnector. 3. "disaster recovery" is what I saw Mickael Maison set up mentioned in this jira (https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-15172)). If you have any good suggestions, I

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #67

See Changes: -- [...truncated 282901 lines...] Gradle Test Run :core:integrationTest > Gradle Test Executor 177 > ZooKeeperClientTest >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #12

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2156

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #66

See Changes: -- [...truncated 282637 lines...] > Task :raft:testClasses UP-TO-DATE > Task :connect:json:testJar > Task :group-coordinator:compileTestJava UP-TO-DATE > Task

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.4 #163

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #11

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2155

See

Re: [VOTE] KIP-970: Deprecate and remove Connect's redundant task configurations endpoint

+1 (non - binding). Thanks ! Sagar. On Wed, 30 Aug 2023 at 11:09 PM, Chris Egerton wrote: > +1 (binding), thanks Yash! > > On Wed, Aug 30, 2023 at 1:34 PM Andrew Schofield < > andrew_schofield_j...@outlook.com> wrote: > > > Thanks for the KIP. Looks good to me. > > > > +1 (non-binding). > > >

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #2154

See

Re: [VOTE] KIP-970: Deprecate and remove Connect's redundant task configurations endpoint

+1 (binding), thanks Yash! On Wed, Aug 30, 2023 at 1:34 PM Andrew Schofield < andrew_schofield_j...@outlook.com> wrote: > Thanks for the KIP. Looks good to me. > > +1 (non-binding). > > Andrew > > > On 30 Aug 2023, at 18:07, Hector Geraldino (BLOOMBERG/ 919 3RD A) < > hgerald...@bloomberg.net>

Re: [VOTE] KIP-970: Deprecate and remove Connect's redundant task configurations endpoint

Thanks for the KIP. Looks good to me. +1 (non-binding). Andrew > On 30 Aug 2023, at 18:07, Hector Geraldino (BLOOMBERG/ 919 3RD A) > wrote: > > This makes sense to me, +1 (non-binding) > > From: dev@kafka.apache.org At: 08/30/23 02:58:59 UTC-4:00To: > dev@kafka.apache.org > Subject: [VOTE]

Re:[VOTE] KIP-970: Deprecate and remove Connect's redundant task configurations endpoint

This makes sense to me, +1 (non-binding) From: dev@kafka.apache.org At: 08/30/23 02:58:59 UTC-4:00To: dev@kafka.apache.org Subject: [VOTE] KIP-970: Deprecate and remove Connect's redundant task configurations endpoint Hi all, This is the vote thread for KIP-970 which proposes deprecating (in

[DISCUSS] KIP-973 Expose per topic replication rate metrics

Relatively minor change that fixes a mismatch between documentation and implementation. https://cwiki.apache.org/confluence/display/KAFKA/KIP-973%3A+Expose+per+topic+replication+rate+metrics

Re: Apache Kafka 3.6.0 release

Hi Satish, Wanted to let you know that KAFKA-12879 ( https://issues.apache.org/jira/browse/KAFKA-12879), a breaking change in Admin::listOffsets, has been reintroduced into the code base. Since we haven't yet published a release with this change (at least, not the more recent instance of it), I

[jira] [Reopened] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reopened KAFKA-12879: --- Assignee: (was: Philip Nee) Reopening due to

Re: Re: [DISCUSS] KIP-972: Add the metric of the current running version of kafka

Hi, Prometheus only support numeric values for metrics. This means it's not able to handle the kafka.server:type=app-info metric since Kafka versions are not valid numbers (3.5.0). As a workaround we could create a metric with the version without the dots, for example with value 350 for Kafka

Re: Apache Kafka 3.6.0 release

Hi, Please plan to continue merging pull requests associated with any outstanding minor features and stabilization changes to 3.6 branch before September 3rd. Kindly update the KIP's implementation status in the 3.6.0 release notes. Thanks, Satish. On Fri, 25 Aug 2023 at 21:37, Justine Olshan

Re: Re: [DISCUSS] KIP-972: Add the metric of the current running version of kafka

Hi, Kamal, thanks your reminding, but I have a question: It seems that I can't get this metric through "jmx_prometheus"? Although I observed this metric through other tools. best, hudeqi Kamal Chandraprakash kamal.chandraprak...@gmail.com写道： > Hi Hudeqi, > > Kafka already emits the version

Re: Re: [DISCUSS] KIP-971 Expose replication-offset-lag MirrorMaker2 metric

Hi Elkhan, I have also done work similar to the partition replication lag mentioned in this kip. After going online, I discovered a problem: when `MirrorSourceTask` executes `poll`, it obtains the LEO of the source topic through the consumer. This logic may take seconds to jitter. , I think

Re: [DISCUSS] KIP-971 Expose replication-offset-lag MirrorMaker2 metric

Hi Elkhan, I think this is quite a useful improvement. A few questions, suggestions: 1. How do you calculate the min, max and avg variants? If I understand correctly then the metric itself is partition based (where replication-offset-lag is the lag of the replica that is being consumed) and these

Re: [DISCUSS] KIP-936: Throttle number of active PIDs

Hi Claude, sorry for the late reply was out for some time. Thanks for your response. > - To ensure that all produced ids are tracked for 1 hour regardless of > whether they were produced by userA or userB. Not really we need to track producer ids created by userA separately from producer ids

[jira] [Resolved] (KAFKA-15412) Reading an unknown version of quorum-state-file should trigger an error

[ https://issues.apache.org/jira/browse/KAFKA-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-15412. --- Fix Version/s: 3.7.0 Resolution: Fixed > Reading an unknown version of quorum-state-file

[VOTE] KIP-970: Deprecate and remove Connect's redundant task configurations endpoint

Hi all, This is the vote thread for KIP-970 which proposes deprecating (in the Apache Kafka 3.7 release) and eventually removing (in the next major Apache Kafka release - 4.0) Connect's redundant task configurations endpoint. KIP -