[jira] [Created] (KAFKA-18120) KIP-891: Support for multiple versions of connect plugins.

2024-11-29 Thread Snehashis Pal (Jira)
Snehashis Pal created KAFKA-18120:
-

 Summary: KIP-891: Support for multiple versions of connect plugins.
 Key: KAFKA-18120
 URL: https://issues.apache.org/jira/browse/KAFKA-18120
 Project: Kafka
  Issue Type: New Feature
  Components: connect
Affects Versions: 4.0.0
Reporter: Snehashis Pal


Jira to track implementation of KIP-891 [KIP-891: Running multiple versions of 
Connector plugins - Apache Kafka - Apache Software 
Foundation|https://cwiki.apache.org/confluence/display/KAFKA/KIP-891%3A+Running+multiple+versions+of+Connector+plugins]

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18121) Add support for duration-based offset reset strategy

2024-11-29 Thread Andrew Schofield (Jira)
Andrew Schofield created KAFKA-18121:


 Summary: Add support for duration-based offset reset strategy
 Key: KAFKA-18121
 URL: https://issues.apache.org/jira/browse/KAFKA-18121
 Project: Kafka
  Issue Type: Sub-task
Reporter: Andrew Schofield
Assignee: Andrew Schofield


This is part of 
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-1106%3A+Add+duration+based+offset+reset+option+for+consumer+clients].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18122) Add ShareConsumeBenchWorker for running trogdor workloads.

2024-11-29 Thread Shivsundar R (Jira)
Shivsundar R created KAFKA-18122:


 Summary: Add ShareConsumeBenchWorker for running trogdor workloads.
 Key: KAFKA-18122
 URL: https://issues.apache.org/jira/browse/KAFKA-18122
 Project: Kafka
  Issue Type: Sub-task
Reporter: Shivsundar R


Add ShareConsumeBenchWorker which will be used to run share consumers on 
trogdor workloads.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18123) Fix flaky DynamicBrokerReconfigurationTest#testThreadPoolResize

2024-11-29 Thread Chia-Ping Tsai (Jira)
Chia-Ping Tsai created KAFKA-18123:
--

 Summary: Fix flaky 
DynamicBrokerReconfigurationTest#testThreadPoolResize
 Key: KAFKA-18123
 URL: https://issues.apache.org/jira/browse/KAFKA-18123
 Project: Kafka
  Issue Type: Bug
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai


The root cause is similar to KAFKA-18098. In kraft mode, the distributions 
includes some randomization, so we can't assume the replica manager can 
distribute those replicas on all replica threads uniformly



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18124) Remove zk migration from tests

2024-11-29 Thread Chia-Ping Tsai (Jira)
Chia-Ping Tsai created KAFKA-18124:
--

 Summary: Remove zk migration from tests
 Key: KAFKA-18124
 URL: https://issues.apache.org/jira/browse/KAFKA-18124
 Project: Kafka
  Issue Type: Sub-task
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai


RaftManagerTest, BrokerLifecycleManagerTest.scala, KafkaConfigTest.scala, and 
ReplicaManagerTest.scala have migration-related tests



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18125) Implement MirrorCheckpointConnector max task limit

2024-11-29 Thread Jarkko Jaakola (Jira)
Jarkko Jaakola created KAFKA-18125:
--

 Summary: Implement MirrorCheckpointConnector max task limit
 Key: KAFKA-18125
 URL: https://issues.apache.org/jira/browse/KAFKA-18125
 Project: Kafka
  Issue Type: Improvement
  Components: mirrormaker
Reporter: Jarkko Jaakola


Mirrormaker 2 MirrorCheckpointConnector currently can create as many tasks as 
globally configured. Primary limiting factor for number of tasks up to the 
configured maximum is the number of known consumer groups. On larger mirrored 
environments where known consumers groups is large this leads to excessive 
amount of checkpoint tasks.

As the offset sync topic is single partition topic there will be excessive 
amount of tasks reading from and writing to this topic. The targeted Kafka 
broker can and will be under heavy burden.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18126) Refactoring to split the GroupMetadataManager in AK

2024-11-29 Thread Alieh Saeedi (Jira)
Alieh Saeedi created KAFKA-18126:


 Summary: Refactoring to split the GroupMetadataManager in AK
 Key: KAFKA-18126
 URL: https://issues.apache.org/jira/browse/KAFKA-18126
 Project: Kafka
  Issue Type: Improvement
Reporter: Alieh Saeedi


With classic groups, consumer groups, share groups and streams groups, there is 
too much logic in a single class in the new group coordinator, which is the 
{{{}GroupMetadataManager{}}}. Even now, before queues are fully implemented and 
before streams groups are added, the unit test class is 14k LOC.

We aim to refactor the class to (at least) split the RPC handling by group type 
- so one class for classic RPCs + helpers, one class for KIP-848 RPCs + 
helpers, one class for share groups and one for streams groups.

We’d still need a common class, since the ID space for groups is shared. One 
idea would be to have a GroupStore which just keeps the metadata for all 
groups, whereas all the RPC handling code is moved to specific classes by 
group, which access the GroupStore.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (KAFKA-16617) Add KRaft info for the `advertised.listeners` doc description

2024-11-29 Thread Chia-Ping Tsai (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-16617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chia-Ping Tsai resolved KAFKA-16617.

Fix Version/s: 4.0.0
   Resolution: Fixed

> Add KRaft info for the `advertised.listeners` doc description
> -
>
> Key: KAFKA-16617
> URL: https://issues.apache.org/jira/browse/KAFKA-16617
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Luke Chen
>Assignee: Chia-Chuan Yu
>Priority: Major
>  Labels: newbie, newbie++
> Fix For: 4.0.0
>
>
> Currently, we only write ZK handler in the `advertised.listeners` doc 
> description:
> > Listeners to publish to ZooKeeper for clients to use, if different than the 
> > listeners config property.
> We should also add KRaft handler info in the doc
> ref: 
> https://kafka.apache.org/documentation/#brokerconfigs_advertised.listeners



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (KAFKA-18127) Handle subscription pattern used with v0 HB broker

2024-11-29 Thread Lianet Magrans (Jira)
Lianet Magrans created KAFKA-18127:
--

 Summary: Handle subscription pattern used with v0 HB broker
 Key: KAFKA-18127
 URL: https://issues.apache.org/jira/browse/KAFKA-18127
 Project: Kafka
  Issue Type: Bug
  Components: consumer
Reporter: Lianet Magrans
Assignee: Lianet Magrans
 Fix For: 4.0.0


Handle the case of consumer.subscribe to SubscriptionPattern used with v0 HB 
brokers (regex not supported). It should throw UnsupportedVersionException on 
the following consumer.poll after the call to subscribe, generated on the 
client side.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #133

2024-11-29 Thread Apache Jenkins Server
See