Matthias J. Sax created KAFKA-8033:
--
Summary: Flaky Test PlaintextConsumerTest#testFetchInvalidOffset
Key: KAFKA-8033
URL: https://issues.apache.org/jira/browse/KAFKA-8033
Project: Kafka
Iss
Matthias J. Sax created KAFKA-8031:
--
Summary: Flaky Test UserClientIdQuotaTest#testQuotaOverrideDelete
Key: KAFKA-8031
URL: https://issues.apache.org/jira/browse/KAFKA-8031
Project: Kafka
Is
Matthias J. Sax created KAFKA-8032:
--
Summary: Flaky Test UserQuotaTest#testQuotaOverrideDelete
Key: KAFKA-8032
URL: https://issues.apache.org/jira/browse/KAFKA-8032
Project: Kafka
Issue Type
Matthias J. Sax created KAFKA-8030:
--
Summary: Flaky Test
TopicCommandWithAdminClientTest#testDescribeUnderMinIsrPartitionsMixed
Key: KAFKA-8030
URL: https://issues.apache.org/jira/browse/KAFKA-8030
P
Hello everybody,
It's been a week since this KIP was first posted and not much discussion
has been had. I can only assume people find the new metric somewhat
reasonable. I will consider starting a voting thread after a couple of days
if nobody has objections.
@Manikumar,
Do you have any further t
Hi Eno,
A control plane needs to do this today because Kafka doesn't provide such
mapping.
I am not sure why we want every control plane figure this out and rather let
this mapping which exists today in Kafka at node level
on disk be at a global level in zookeeper.
If we implement this, any cont
[
https://issues.apache.org/jira/browse/KAFKA-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7997.
--
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request 6324
[https://github.com/a
Hi Harsha, Li Kan,
What Colin mentioned is what I see in practice as well (at AWS and our
clusters). A control plane management tool decides the mapping
hostname-broker ID and can change it as it sees fit as brokers fail and new
ones are brought in. That control plane usually already has a databas
