[jira] [Created] (KAFKA-16876) TaskManager.handleRevocation doesn't handle errors thrown from task.prepareCommit

Rohan Desai created KAFKA-16876: --- Summary: TaskManager.handleRevocation doesn't handle errors thrown from task.prepareCommit Key: KAFKA-16876 URL: https://issues.apache.org/jira/browse/KAFKA-16876 Proje

[jira] [Created] (KAFKA-16875) Replace ClientState with TaskAssignment when creating individual consumer Assignments

A. Sophie Blee-Goldman created KAFKA-16875: -- Summary: Replace ClientState with TaskAssignment when creating individual consumer Assignments Key: KAFKA-16875 URL: https://issues.apache.org/jira/browse/KAFK

[jira] [Created] (KAFKA-16874) Remove old TaskAssignor interface

A. Sophie Blee-Goldman created KAFKA-16874: -- Summary: Remove old TaskAssignor interface Key: KAFKA-16874 URL: https://issues.apache.org/jira/browse/KAFKA-16874 Project: Kafka Issue T

[jira] [Created] (KAFKA-16873) Remove StreamsConfig.INTERNAL_TASK_ASSIGNOR_CLASS

A. Sophie Blee-Goldman created KAFKA-16873: -- Summary: Remove StreamsConfig.INTERNAL_TASK_ASSIGNOR_CLASS Key: KAFKA-16873 URL: https://issues.apache.org/jira/browse/KAFKA-16873 Project: Kafka

[jira] [Created] (KAFKA-16872) Remove ClientState class

A. Sophie Blee-Goldman created KAFKA-16872: -- Summary: Remove ClientState class Key: KAFKA-16872 URL: https://issues.apache.org/jira/browse/KAFKA-16872 Project: Kafka Issue Type: Sub-

[jira] [Created] (KAFKA-16871) Clean up internal AssignmentConfigs class in Streams

A. Sophie Blee-Goldman created KAFKA-16871: -- Summary: Clean up internal AssignmentConfigs class in Streams Key: KAFKA-16871 URL: https://issues.apache.org/jira/browse/KAFKA-16871 Project: Kafk

[jira] [Created] (KAFKA-16870) Values.parseString returns objects which fail ConnectSchema.validateValue

Greg Harris created KAFKA-16870: --- Summary: Values.parseString returns objects which fail ConnectSchema.validateValue Key: KAFKA-16870 URL: https://issues.apache.org/jira/browse/KAFKA-16870 Project: Kafk

[jira] [Created] (KAFKA-16869) Rewrite HighAvailabilityTaskAssignor to implement the new TaskAssignor interface

A. Sophie Blee-Goldman created KAFKA-16869: -- Summary: Rewrite HighAvailabilityTaskAssignor to implement the new TaskAssignor interface Key: KAFKA-16869 URL: https://issues.apache.org/jira/browse/KAFKA-168

[jira] [Created] (KAFKA-16868) Post KIP-924 StreamsPartitionAssignor code cleanup

A. Sophie Blee-Goldman created KAFKA-16868: -- Summary: Post KIP-924 StreamsPartitionAssignor code cleanup Key: KAFKA-16868 URL: https://issues.apache.org/jira/browse/KAFKA-16868 Project: Kafka

Re: [DISCUSS] KIP-924: customizable task assignment for Streams

Hi all! Coming in with hopefully the last set of minor updates. During implementation of the new out-of-the-box assignors and the TaskAssignmentUtils which make heavy use of the new API, we determined a few quality-of-life improvements were needed to make some of the new classes/methods a bit easie

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

See

[jira] [Created] (KAFKA-16867) Streams should run tag-based standby assignment based on rack ids

A. Sophie Blee-Goldman created KAFKA-16867: -- Summary: Streams should run tag-based standby assignment based on rack ids Key: KAFKA-16867 URL: https://issues.apache.org/jira/browse/KAFKA-16867

[jira] [Resolved] (KAFKA-16864) Copy on write in the Optimized Uniform Assignor

[ https://issues.apache.org/jira/browse/KAFKA-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16864. - Fix Version/s: 3.8.0 Resolution: Fixed > Copy on write in the Optimized Uniform Assignor

[jira] [Resolved] (KAFKA-16860) Introduce `group.version` feature flag

[ https://issues.apache.org/jira/browse/KAFKA-16860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16860. - Resolution: Fixed > Introduce `group.version` feature flag > ---

[jira] [Resolved] (KAFKA-16639) AsyncKafkaConsumer#close does not send heartbeat to leave group

[ https://issues.apache.org/jira/browse/KAFKA-16639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16639. Resolution: Fixed > AsyncKafkaConsumer#close does not send heartbeat to leave group >

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

See

Re: [DISCUSS] Apache Kafka 3.8.0 release

Makes sense to me. On Fri, May 31, 2024 at 2:05 AM Luke Chen wrote: > Hi Justine, > > In the KIP-1012 discussion thread > , our > conclusion should be having an "automatic" unclean leader election in > KRaft, even if KIP-966 canno

Re: [DISCUSS] KIP-877: Mechanism for plugins and connectors to register metrics

Hi Mickael, Apologies for the delay, and many thanks for the updates to the KIP. I'm happy with the proposal to automatically close metrics for plugins, even though it does come at the cost of dropping the new AbstractConfig::getConfiguredInstance and AbstractConfig::getConfiguredInstances variant

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.8 #1

See Changes: -- [...truncated 519584 lines...] [2024-05-31T14:28:52.106Z] [2024-05-31T14:28:52.106Z] Gradle Test Run :core:test > Gradle Test Executor 99 > KafkaZkClientTest >

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.4 #174

See

Re: [DISCUSS] KIP-877: Mechanism for plugins and connectors to register metrics

Bumping this thread. If there are no other comments, I'll restart a vote in the next couple of weeks. Thanks, Mickael On Thu, Apr 25, 2024 at 3:28 PM Mickael Maison wrote: > > Hi Greg, > > Thanks for taking a close look at the KIP. > > 1/2) I understand your concern about leaking resources. I'v

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

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.0 #224

See Changes: -- [...truncated 357337 lines...] [2024-05-31T12:45:39.698Z] [INFO] --- site:3.5.1:attach-descriptor (attach-descriptor) @ streams-quickstart --- [2024-05-31T12:

RE: standalone race condition?

To add to my own comments 😊 I’ve put debug on to the adapter that’s failing more than the others and I observe that sometimes it fails to start up and sometimes it doesn’t. Either way the call back to the REST interface to tell it that it can return back to the API doesn’t work and the original

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

See Changes: -- [...truncated 367164 lines...] [2024-05-31T12:04:16.052Z] > Task :connect:api:javadoc [2024-05-31T12:04:16.052Z] > Task :connect:api:copyDependantLibs UP-TO-DA

[jira] [Resolved] (KAFKA-16629) add broker-related tests to ConfigCommandIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-16629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16629. Fix Version/s: 3.9.0 Resolution: Fixed > add broker-related tests to ConfigCommandI

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

See Changes: -- [...truncated 88093 lines...] [2024-05-31T10:41:37.452Z] [2024-05-31T10:41:37.452Z] BUILD SUCCESSFUL in 2m 18s [2024-05-31T10:41:37.452Z] 79 actionable tasks:

Re: New release branch 3.8.0

Correction, trunk is not actually bumped, but a PR is ready to review. Best, On Fri, May 31, 2024 at 11:13 AM Josep Prat wrote: > Hello Kafka developers and friends, > > As promised, we now have a release branch for 3.8 release. > Trunk has been bumped to 3.9.0-SNAPSHOT. > > I'll be going over

New release branch 3.8.0

Hello Kafka developers and friends, As promised, we now have a release branch for 3.8 release. Trunk has been bumped to 3.9.0-SNAPSHOT. I'll be going over the JIRAs to move every non-blocker from this release to the next release. >From this point, most changes should go to trunk. - Blockers (exi

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Justine, In the KIP-1012 discussion thread , our conclusion should be having an "automatic" unclean leader election in KRaft, even if KIP-966 cannot complete in time. > We should specify in KIP-1012 that we need to have some way

[jira] [Resolved] (KAFKA-16824) Utils.getHost and Utils.getPort do not catch a lot of invalid host and ports

[ https://issues.apache.org/jira/browse/KAFKA-16824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-16824. --- Fix Version/s: 3.8.0 Resolution: Fixed > Utils.getHost and Utils.getPort do not catch a lot o

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

See