[jira] [Resolved] (KAFKA-12380) Executor in Connect's Worker is not shut down when the worker is

[ https://issues.apache.org/jira/browse/KAFKA-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-12380. --- Fix Version/s: 3.3.0 Resolution: Fixed > Executor in Connect's Worker is not shut down when

[jira] [Resolved] (KAFKA-13859) SCRAM authentication issues with kafka-clients 3.0.1

[ https://issues.apache.org/jira/browse/KAFKA-13859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dengziming resolved KAFKA-13859. Resolution: Not A Problem In

Re: Possible Bug: kafka-reassign-partitions causing the data retention time to be reset

Thanks for your help! I'm not sure how that would help me though. I'm not actually trying to decommission a Kafka broker. I would like to move all the data from one disk (log.dir) to another within the same broker while keeping the original modification time of the moved segment files. After that

[jira] [Created] (KAFKA-13861) validateOnly request field does not work for CreatePartition requests in Kraft mode.

Akhilesh Chaganti created KAFKA-13861: - Summary: validateOnly request field does not work for CreatePartition requests in Kraft mode. Key: KAFKA-13861 URL: https://issues.apache.org/jira/browse/KAFKA-13861

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #109

See Changes: -- [...truncated 505321 lines...] [2022-04-28T17:46:51.752Z] [2022-04-28T17:46:51.752Z] ZooKeeperClientTest > testZNodeChangeHandlerForDeletion() STARTED

Re: Possible Bug: kafka-reassign-partitions causing the data retention time to be reset

The resource (https://mike.seid.io/blog/decommissiong-a-kafka-node.html) may help you. I have created (https://issues.apache.org/jira/browse/KAFKA-13860) to replay the case . On Thu, Apr 28, 2022 at 10:33 PM Fares Oueslati wrote: > Hello, > > I'm not sure how to report this properly but I

[jira] [Created] (KAFKA-13860) add Decommissioning feature to kafka-reassign-partitions.sh

lqjacklee created KAFKA-13860: - Summary: add Decommissioning feature to kafka-reassign-partitions.sh Key: KAFKA-13860 URL: https://issues.apache.org/jira/browse/KAFKA-13860 Project: Kafka

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.2 #41

See

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

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #108

See Changes: -- [...truncated 439762 lines...] [2022-04-28T15:31:14.935Z] > Task :metadata:testClasses UP-TO-DATE [2022-04-28T15:31:14.935Z] > Task

Possible Bug: kafka-reassign-partitions causing the data retention time to be reset

Hello, I'm not sure how to report this properly but I didn't get any answer in the user mailing list. In order to remove a disk in a JBOD setup, I moved all data from one disk to another on every Kafka broker using kafka-reassign-partitions, then I went through some weird behaviour. Basically,

[jira] [Resolved] (KAFKA-6084) ReassignPartitionsCommand should propagate JSON parsing failures

[ https://issues.apache.org/jira/browse/KAFKA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-6084. Fix Version/s: 2.8.0 Resolution: Fixed > ReassignPartitionsCommand should

Not Able to Update Replication Factor of Kafka Topic

Hi Team, We have a 3 node kafka-zookeeper cluster setup with kafka-zookeeper communicating on SSL. We are currently using apache kafka 2.5 and zookeeper 3.5.7 . We are trying to increase the replication factor in kafka topics using the below method: To increase the number of replicas for a given

Re: [VOTE] 3.1.1 RC0

Hi Tom, I merged and cherry-picked the fix. Ismael On Thu, Apr 28, 2022 at 12:33 AM Tom Bentley wrote: > Hi Dongjoon, > > I apologise, I should have been a bit more communicative. I was waiting for > a better fix to the issue previously highlighted by David. Ismael has > kindly provided a

Re: [VOTE] 3.1.1 RC0

Hi Dongjoon, I think it makes sense to go with 3.1.1 for the Spark release you are currently stabilizing. Ismael On Wed, Apr 27, 2022 at 1:54 PM Dongjoon Hyun wrote: > Hi, All. > > It seems that Apache Kafka 3.2.0 RC0 vote started already instead of > Apache Kafka 3.1.1 release. > > Does

[jira] [Resolved] (KAFKA-13442) REST API endpoint for fetching a connector's config definition

[ https://issues.apache.org/jira/browse/KAFKA-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-13442. - Resolution: Duplicate > REST API endpoint for fetching a connector's config

[jira] [Resolved] (KAFKA-13452) MM2 creates invalid checkpoint when offset mapping is not available

[ https://issues.apache.org/jira/browse/KAFKA-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-13452. - Resolution: Duplicate > MM2 creates invalid checkpoint when offset mapping is

Re: [kafka-clients] Re: [VOTE] 3.2.0 RC0

Hi Luke, Thanks for your message! I agree and I will include this PR in the next RC. Best, Bruno On 28.04.22 09:38, Luke Chen wrote: Hi Bruno, I think this PR might also need to be included in next release candidate because it's a bug fix/optimization for an issue introduced in v3.2.0.

Re: [kafka-clients] Re: [VOTE] 3.2.0 RC0

Hi Bruno, I think this PR might also need to be included in next release candidate because it's a bug fix/optimization for an issue introduced in v3.2.0. https://github.com/apache/kafka/pull/12096 cc Ismael Thank you. Luke On Thu, Apr 28, 2022 at 3:36 AM Guozhang Wang wrote: > Hi Bruno, > >

Re: [VOTE] 3.1.1 RC0

Hi Dongjoon, I apologise, I should have been a bit more communicative. I was waiting for a better fix to the issue previously highlighted by David. Ismael has kindly provided a patch [1], so I will roll RC1 once this is merged and cherry-picked. Kind regards, Tom [1]: