Sushant Mahajan created KAFKA-18828:
---
Summary: Update share group metrics code in group coordinator
Key: KAFKA-18828
URL: https://issues.apache.org/jira/browse/KAFKA-18828
Project: Kafka
Is
Sushant Mahajan created KAFKA-18827:
---
Summary: Initialize share group state impl
Key: KAFKA-18827
URL: https://issues.apache.org/jira/browse/KAFKA-18827
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-18799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18799.
Fix Version/s: 4.1.0
Resolution: Fixed
> Remove AdminUtils
> -
>
>
Hi Olasoji,
Thanks for the KIP! I find it addresses many of the concerns I had with
KIP-984. Thank you for following up on that!
1. Since the Compression interface is internal currently, it may contain
some components that were not designed with pluggability in mind, such as
the static methods. A
[
https://issues.apache.org/jira/browse/KAFKA-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kaushik Raina resolved KAFKA-18684.
---
Resolution: Done
> Implement new base exception classes
> --
Hi Greg:
I see you are from a very practical point of view to evaluate this KIP. With
tiered storage already merged in it is hard to accept another improvement that
provide similar solution, even it is better by design and enable potential
future growth.
That being said. This is still a communi
After waiting the prescribed 72 hours, I would like to re-close this vote
:)
The results are:
* 7 binding +1 from Ismael, Bruno, Chia-Ping, Andrew, David J, Matthias,
and Kamal
* 2 non-binding +1 community votes from Ukpa and TengYao
* No -1 votes
*Now* the KIP is accepted.
Thanks all,
David
On
Hi, I would like to bring this back to everyone's attention. This KIP
introduces a simple framework that enables the use of alternative, faster
implementations of the existing compression codecs (Gzip, Snappy, Zstandard and
LZ4) in Kafka.
https://cwiki.apache.org/confluence/x/Xgr0Ew
Thanks
Hi All,
Thanks for this amazing KIP! I'm glad that Kafka is getting more accessible
multi-tenancy features, beyond the primitives that are already available.
1. I think one concept for hierarchical VCs could be to make it so there is
a "root VC" corresponding to the physical cluster, and define t
Bill Bejeck created KAFKA-18826:
---
Summary: Add Global Thread Metrics
Key: KAFKA-18826
URL: https://issues.apache.org/jira/browse/KAFKA-18826
Project: Kafka
Issue Type: Task
Affects Versions
Hi De Gao,
Thanks for your explanation. It sounds like this feature is appropriate in
situations where:
1. Low latency to change replicas is a high priority
2. External storage is unavailable or undesirable
3. Linear growth in metadata size is acceptable to clients, brokers, and
controllers
4. Da
+1 (binding)
Thanks for the KIP!
On Wed, Feb 5, 2025 at 8:06 AM Sophie Blee-Goldman
wrote:
>
> +1 (binding)
>
> Thanks for the KIP! Neat and practical idea
>
> On Tue, Feb 4, 2025 at 10:52 AM Almog Gavra wrote:
>
> > Hello All,
> >
> > I'd like to start a vote on KIP-1127. Please take a look at
[
https://issues.apache.org/jira/browse/KAFKA-18773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18773.
Resolution: Fixed
trunk:
https://github.com/apache/kafka/commit/1132f08c57d46e80bc502965a
[
https://issues.apache.org/jira/browse/KAFKA-18524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamal Chandraprakash resolved KAFKA-18524.
--
Fix Version/s: 4.1.0
Resolution: Duplicate
> Fix flaky
> RemoteIndexCa
[
https://issues.apache.org/jira/browse/KAFKA-18089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamal Chandraprakash resolved KAFKA-18089.
--
Fix Version/s: 4.1.0
Resolution: Fixed
> RemoteIndexCacheTest fails wit
Kamal Chandraprakash created KAFKA-18825:
Summary: Fix the flaky EligibleLeaderReplicasIntegrationTest
Key: KAFKA-18825
URL: https://issues.apache.org/jira/browse/KAFKA-18825
Project: Kafka
TengYao Chi created KAFKA-18824:
---
Summary: Update docs of docker hub to add dynamic voters
description
Key: KAFKA-18824
URL: https://issues.apache.org/jira/browse/KAFKA-18824
Project: Kafka
Is
[
https://issues.apache.org/jira/browse/KAFKA-18767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield resolved KAFKA-18767.
--
Fix Version/s: 4.1.0
Resolution: Fixed
> Add client side config check for share
Chia-Ping Tsai created KAFKA-18823:
--
Summary: native docker don't honor the result of checking sign key
Key: KAFKA-18823
URL: https://issues.apache.org/jira/browse/KAFKA-18823
Project: Kafka
Hi Luke,
1. ACL after migrating to VC:
Suppose we have an ACL entry to user Bob, after Bob joining VC1, how does
the ACL migration work?
Will Bob still have the ACL in cluster-wide level?
Yes, we didn't plan for this originally, so it would be the administrator's
responsibility to migrate existin
黃竣陽 created KAFKA-18822:
---
Summary: Fail test LoggingResourceTest#testSetLevelDefaultScope,
testSetLevelInvalidScope
Key: KAFKA-18822
URL: https://issues.apache.org/jira/browse/KAFKA-18822
Project: Kafka
Hi YengTao,
Yes, we left out the naming mechanism but not intentionally. I'll add it
after answering your feedback.
- Will this leverage Kafka's existing UUID mechanism, or are there plans
to implement a new naming mechanism?
- Will there be standardized formats for the length and structu
JieFang.He created KAFKA-18821:
--
Summary: There seems to be a problem with the partition replica
synchronization mechanism for empty data
Key: KAFKA-18821
URL: https://issues.apache.org/jira/browse/KAFKA-18821
Vishal created KAFKA-18820:
--
Summary: CVE-2025-24970 [netty-handler] [4.1.111.Final]
Key: KAFKA-18820
URL: https://issues.apache.org/jira/browse/KAFKA-18820
Project: Kafka
Issue Type: Bug
Affect
[
https://issues.apache.org/jira/browse/KAFKA-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Wang resolved KAFKA-18801.
Fix Version/s: 4.1.0
Reviewer: Chia-Ping Tsai
Resolution: Fixed
> Remove ClusterGe
[
https://issues.apache.org/jira/browse/KAFKA-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield reopened KAFKA-17853:
--
The issue still occurs if the broker is not available.
If you run `kafka-console-consumer
Lucas Brutschy created KAFKA-18819:
--
Summary: StreamsGroupHeartbeat API and StreamsGroupDescribe API
must check topic describe
Key: KAFKA-18819
URL: https://issues.apache.org/jira/browse/KAFKA-18819
Shubham Raj created KAFKA-18818:
---
Summary: Significant delay in Metadata Update After Admin Client
Operations in KRaft Mode
Key: KAFKA-18818
URL: https://issues.apache.org/jira/browse/KAFKA-18818
Projec
[
https://issues.apache.org/jira/browse/KAFKA-18798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18798.
Fix Version/s: 4.1.0
Resolution: Fixed
> The replica placement policy used by Reass
29 matches
Mail list logo