[jira] [Commented] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800845#comment-17800845 ] Ron Dagostino commented on KAFKA-15495: --- Thanks, [~jsancio]. I've updated the title and

[jira] [Updated] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Description: Assume a topic-partition has just a single leader replica in the ISR. Assume

[jira] [Updated] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Affects Version/s: 2.2.1 2.3.0 2.1.1

[jira] [Updated] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Affects Version/s: 2.7.2 2.6.3 3.1.0

[jira] [Updated] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Affects Version/s: 3.2.1 3.1.2 3.0.2

[jira] [Updated] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Affects Version/s: 3.6.1 3.5.2 3.5.0

[jira] [Updated] (KAFKA-15495) Partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Summary: Partition truncated when the only ISR member restarts with an empty disk (was:

[jira] [Updated] (KAFKA-15365) Broker-side replica management changes

[ https://issues.apache.org/jira/browse/KAFKA-15365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15365: -- Fix Version/s: 3.7.0 > Broker-side replica management changes >

[jira] [Updated] (KAFKA-15358) QueuedReplicaToDirAssignments metric

[ https://issues.apache.org/jira/browse/KAFKA-15358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15358: -- Fix Version/s: 3.7.0 > QueuedReplicaToDirAssignments metric >

[jira] [Updated] (KAFKA-15471) Allow independently stop KRaft controllers or brokers

[ https://issues.apache.org/jira/browse/KAFKA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15471: -- Fix Version/s: 3.7.0 > Allow independently stop KRaft controllers or brokers >

[jira] [Resolved] (KAFKA-15471) Allow independently stop KRaft controllers or brokers

[ https://issues.apache.org/jira/browse/KAFKA-15471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-15471. --- Resolution: Fixed > Allow independently stop KRaft controllers or brokers >

[jira] [Commented] (KAFKA-15710) KRaft support in ServerShutdownTest

[ https://issues.apache.org/jira/browse/KAFKA-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782236#comment-17782236 ] Ron Dagostino commented on KAFKA-15710: --- The KRaft equivalent of

[jira] [Commented] (KAFKA-15591) Trogdor produce workload reports errors in KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-15591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774570#comment-17774570 ] Ron Dagostino commented on KAFKA-15591: --- > Is this caused by that in KRaft protocal, Kafka doesn't

[jira] [Commented] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768787#comment-17768787 ] Ron Dagostino commented on KAFKA-15495: --- Yes. The Disk UUID from JBOD is not needed for this

[jira] [Commented] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768674#comment-17768674 ] Ron Dagostino commented on KAFKA-15495: --- Thanks, Ismael. Yes, I read [the

[jira] [Updated] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Description: Assume a topic-partition in KRaft has just a single leader replica in the ISR.

[jira] [Updated] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Description: Assume a topic-partition in KRaft has just a single leader replica in the ISR.

[jira] [Updated] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Description: Assume a topic-partition in KRaft has just a single leader replica in the ISR.

[jira] [Updated] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with an empty disk

[ https://issues.apache.org/jira/browse/KAFKA-15495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15495: -- Summary: KRaft partition truncated when the only ISR member restarts with an empty disk

[jira] [Created] (KAFKA-15495) KRaft partition truncated when the only ISR member restarts with and empty disk

Ron Dagostino created KAFKA-15495: - Summary: KRaft partition truncated when the only ISR member restarts with and empty disk Key: KAFKA-15495 URL: https://issues.apache.org/jira/browse/KAFKA-15495

[jira] [Resolved] (KAFKA-15219) Support delegation tokens in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-15219. --- Fix Version/s: 3.6.0 Resolution: Fixed > Support delegation tokens in KRaft >

[jira] [Updated] (KAFKA-15098) KRaft migration does not proceed and broker dies if authorizer.class.name is set

[ https://issues.apache.org/jira/browse/KAFKA-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-15098: -- Description: [ERROR] 2023-06-16 20:14:14,298 [main] kafka.Kafka$ - Exiting Kafka due to

[jira] [Created] (KAFKA-15098) KRaft migration does not proceed and broker dies if authorizer.class.name is set

Ron Dagostino created KAFKA-15098: - Summary: KRaft migration does not proceed and broker dies if authorizer.class.name is set Key: KAFKA-15098 URL: https://issues.apache.org/jira/browse/KAFKA-15098

[jira] [Created] (KAFKA-15039) Reduce logging level to trace in PartitionChangeBuilder.tryElection()

Ron Dagostino created KAFKA-15039: - Summary: Reduce logging level to trace in PartitionChangeBuilder.tryElection() Key: KAFKA-15039 URL: https://issues.apache.org/jira/browse/KAFKA-15039 Project:

[jira] [Updated] (KAFKA-14887) ZK session timeout can cause broker to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14887: -- Fix Version/s: 2.7.3 3.2.4 3.1.3

[jira] [Updated] (KAFKA-14887) ZK session timeout can cause broker to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14887: -- Fix Version/s: 3.5.0 > ZK session timeout can cause broker to shutdown >

[jira] [Resolved] (KAFKA-14735) Improve KRaft metadata image change performance at high topic counts

[ https://issues.apache.org/jira/browse/KAFKA-14735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14735. --- Resolution: Fixed > Improve KRaft metadata image change performance at high topic counts >

[jira] [Resolved] (KAFKA-14890) Kafka initiates shutdown due to connectivity problem with Zookeeper and FatalExitError from ChangeNotificationProcessorThread

[ https://issues.apache.org/jira/browse/KAFKA-14890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14890. --- Resolution: Duplicate Duplicate of https://issues.apache.org/jira/browse/KAFKA-14887 >

[jira] [Assigned] (KAFKA-14887) ZK session timeout can cause broker to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino reassigned KAFKA-14887: - Assignee: Ron Dagostino > ZK session timeout can cause broker to shutdown >

[jira] [Created] (KAFKA-14887) ZK session timeout can cause broker to shutdown

Ron Dagostino created KAFKA-14887: - Summary: ZK session timeout can cause broker to shutdown Key: KAFKA-14887 URL: https://issues.apache.org/jira/browse/KAFKA-14887 Project: Kafka Issue

[jira] [Resolved] (KAFKA-14351) Implement controller mutation quotas in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14351. --- Fix Version/s: 3.5.0 Resolution: Fixed > Implement controller mutation quotas in

[jira] [Created] (KAFKA-14735) Improve KRaft metadata image change performance at high topic counts

Ron Dagostino created KAFKA-14735: - Summary: Improve KRaft metadata image change performance at high topic counts Key: KAFKA-14735 URL: https://issues.apache.org/jira/browse/KAFKA-14735 Project:

[jira] [Comment Edited] (KAFKA-14731) Upgrade ZooKeeper to 3.6.4

[ https://issues.apache.org/jira/browse/KAFKA-14731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690531#comment-17690531 ] Ron Dagostino edited comment on KAFKA-14731 at 2/17/23 6:39 PM: Fixes in

[jira] [Commented] (KAFKA-14731) Upgrade ZooKeeper to 3.6.4

[ https://issues.apache.org/jira/browse/KAFKA-14731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690531#comment-17690531 ] Ron Dagostino commented on KAFKA-14731: --- Fixes in 3.6.4:

[jira] [Created] (KAFKA-14731) Upgrade ZooKeeper to 3.6.4

Ron Dagostino created KAFKA-14731: - Summary: Upgrade ZooKeeper to 3.6.4 Key: KAFKA-14731 URL: https://issues.apache.org/jira/browse/KAFKA-14731 Project: Kafka Issue Type: Task Affects

[jira] [Updated] (KAFKA-14661) Upgrade Zookeeper to 3.8.1

[ https://issues.apache.org/jira/browse/KAFKA-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14661: -- Fix Version/s: (was: 3.4.1) (was: 3.3.3) > Upgrade Zookeeper to

[jira] [Resolved] (KAFKA-14711) kafaka-metadata-quorum.sh does not honor --command-config

[ https://issues.apache.org/jira/browse/KAFKA-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14711. --- Resolution: Fixed > kafaka-metadata-quorum.sh does not honor --command-config >

[jira] [Created] (KAFKA-14711) kafaka-metadata-quorum.sh does not honor --command-config

Ron Dagostino created KAFKA-14711: - Summary: kafaka-metadata-quorum.sh does not honor --command-config Key: KAFKA-14711 URL: https://issues.apache.org/jira/browse/KAFKA-14711 Project: Kafka

[jira] [Assigned] (KAFKA-14351) Implement controller mutation quotas in KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino reassigned KAFKA-14351: - Assignee: Ron Dagostino > Implement controller mutation quotas in KRaft >

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Fix Version/s: 3.4.0 (was: 3.5.0) > KRaft broker heartbeat timeout

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Affects Version/s: (was: 3.4.0) > KRaft broker heartbeat timeout should not exceed

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Affects Version/s: (was: 3.3.2) > KRaft broker heartbeat timeout should not exceed

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Fix Version/s: 3.3.2 > KRaft broker heartbeat timeout should not exceed

[jira] [Resolved] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14392. --- Fix Version/s: 3.5.0 Resolution: Fixed > KRaft broker heartbeat timeout should not

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Affects Version/s: 3.3.2 > KRaft broker heartbeat timeout should not exceed

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Affects Version/s: 3.4.0 > KRaft broker heartbeat timeout should not exceed

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Component/s: kraft > KRaft broker heartbeat timeout should not exceed

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Affects Version/s: (was: 3.4.0) > KRaft broker heartbeat timeout should not exceed

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Affects Version/s: 3.3.1 3.3.0 3.4.0 > KRaft

[jira] [Commented] (KAFKA-14394) BrokerToControllerChannelManager has 2 separate timeouts

[ https://issues.apache.org/jira/browse/KAFKA-14394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637404#comment-17637404 ] Ron Dagostino commented on KAFKA-14394: --- As per

[jira] [Resolved] (KAFKA-14394) BrokerToControllerChannelManager has 2 separate timeouts

[ https://issues.apache.org/jira/browse/KAFKA-14394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14394. --- Resolution: Not A Problem > BrokerToControllerChannelManager has 2 separate timeouts >

[jira] [Created] (KAFKA-14394) BrokerToControllerChannelManager has 2 separate timeouts

Ron Dagostino created KAFKA-14394: - Summary: BrokerToControllerChannelManager has 2 separate timeouts Key: KAFKA-14394 URL: https://issues.apache.org/jira/browse/KAFKA-14394 Project: Kafka

[jira] [Commented] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634471#comment-17634471 ] Ron Dagostino commented on KAFKA-14392: --- One possibility is to continue to use

[jira] [Updated] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

[ https://issues.apache.org/jira/browse/KAFKA-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14392: -- Summary: KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms (was:

[jira] [Created] (KAFKA-14392) KRaft should comment controller.socket.timeout.ms <= broker.session.timeout.ms

Ron Dagostino created KAFKA-14392: - Summary: KRaft should comment controller.socket.timeout.ms <= broker.session.timeout.ms Key: KAFKA-14392 URL: https://issues.apache.org/jira/browse/KAFKA-14392

[jira] [Created] (KAFKA-14371) quorum-state file contains empty/unused clusterId field

Ron Dagostino created KAFKA-14371: - Summary: quorum-state file contains empty/unused clusterId field Key: KAFKA-14371 URL: https://issues.apache.org/jira/browse/KAFKA-14371 Project: Kafka

[jira] [Created] (KAFKA-14195) Fix KRaft AlterConfig policy usage for Legacy/Full case

Ron Dagostino created KAFKA-14195: - Summary: Fix KRaft AlterConfig policy usage for Legacy/Full case Key: KAFKA-14195 URL: https://issues.apache.org/jira/browse/KAFKA-14195 Project: Kafka

[jira] [Resolved] (KAFKA-14051) KRaft remote controllers do not create metrics reporters

[ https://issues.apache.org/jira/browse/KAFKA-14051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-14051. --- Resolution: Fixed > KRaft remote controllers do not create metrics reporters >

[jira] [Created] (KAFKA-14105) Remove quorum.all_non_upgrade for system tests

Ron Dagostino created KAFKA-14105: - Summary: Remove quorum.all_non_upgrade for system tests Key: KAFKA-14105 URL: https://issues.apache.org/jira/browse/KAFKA-14105 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-14057) Support dynamic reconfiguration in KRaft remote controllers

Ron Dagostino created KAFKA-14057: - Summary: Support dynamic reconfiguration in KRaft remote controllers Key: KAFKA-14057 URL: https://issues.apache.org/jira/browse/KAFKA-14057 Project: Kafka

[jira] [Updated] (KAFKA-14057) Support dynamic reconfiguration in KRaft remote controllers

[ https://issues.apache.org/jira/browse/KAFKA-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-14057: -- Description: We currently do not support dynamic reconfiguration of KRaft remote

[jira] [Created] (KAFKA-14056) Test reading of old messages formats in ZK-to-KRaft upgrade test

Ron Dagostino created KAFKA-14056: - Summary: Test reading of old messages formats in ZK-to-KRaft upgrade test Key: KAFKA-14056 URL: https://issues.apache.org/jira/browse/KAFKA-14056 Project: Kafka

[jira] [Assigned] (KAFKA-14051) KRaft remote controllers do not create metrics reporters

[ https://issues.apache.org/jira/browse/KAFKA-14051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino reassigned KAFKA-14051: - Assignee: Ron Dagostino > KRaft remote controllers do not create metrics reporters >

[jira] [Created] (KAFKA-14051) KRaft remote controllers do not create metrics reporters

Ron Dagostino created KAFKA-14051: - Summary: KRaft remote controllers do not create metrics reporters Key: KAFKA-14051 URL: https://issues.apache.org/jira/browse/KAFKA-14051 Project: Kafka

[jira] [Commented] (KAFKA-13582) `TestVerifiableProducer. test_multiple_kraft_security_protocols` consistently fails

[ https://issues.apache.org/jira/browse/KAFKA-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472008#comment-17472008 ] Ron Dagostino commented on KAFKA-13582: --- This is purely a test configuration issue. An example

[jira] [Commented] (KAFKA-13502) Support configuring BROKER_LOGGER on controller-only KRaft nodes

[ https://issues.apache.org/jira/browse/KAFKA-13502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461478#comment-17461478 ] Ron Dagostino commented on KAFKA-13502: --- This is one aspect of the broader problem as described in

[jira] [Commented] (KAFKA-13552) Unable to dynamically change broker log levels on KRaft

[ https://issues.apache.org/jira/browse/KAFKA-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461476#comment-17461476 ] Ron Dagostino commented on KAFKA-13552: --- [~dengziming] Thanks for pointing that out. Although

[jira] [Updated] (KAFKA-13552) Unable to dynamically change broker log levels on KRaft

[ https://issues.apache.org/jira/browse/KAFKA-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13552: -- Description: It is currently not possible to dynamically change the log level in KRaft. For

[jira] [Created] (KAFKA-13552) Unable to dynamically change broker log levels on KRaft

Ron Dagostino created KAFKA-13552: - Summary: Unable to dynamically change broker log levels on KRaft Key: KAFKA-13552 URL: https://issues.apache.org/jira/browse/KAFKA-13552 Project: Kafka

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Priority: Blocker (was: Major) > Tighten KRaft config checks/constraints >

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Description: We need to tighten the configuration constraints/checks related to KRaft

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Component/s: kraft > Tighten KRaft config checks/constraints >

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Fix Version/s: 3.1.0 > Tighten KRaft config checks/constraints >

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Summary: Tighten KRaft config checks/constraints (was: controller.listener.names is required

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Affects Version/s: (was: 3.1.0) > Tighten KRaft config checks/constraints >

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Fix Version/s: (was: 3.1.0) > Tighten KRaft config checks/constraints >

[jira] [Updated] (KAFKA-13456) controller.listener.names is required for all KRaft nodes, not just controllers

[ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13456: -- Description: The controller.listener.names config is currently checked for existence when the

[jira] [Created] (KAFKA-13456) controller.listener.names is required for all KRaft nodes, not just controllers

Ron Dagostino created KAFKA-13456: - Summary: controller.listener.names is required for all KRaft nodes, not just controllers Key: KAFKA-13456 URL: https://issues.apache.org/jira/browse/KAFKA-13456

[jira] [Comment Edited] (KAFKA-13140) KRaft brokers do not expose kafka.controller metrics, breaking backwards compatibility

[ https://issues.apache.org/jira/browse/KAFKA-13140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443850#comment-17443850 ] Ron Dagostino edited comment on KAFKA-13140 at 11/15/21, 2:25 PM: -- No

[jira] [Updated] (KAFKA-13270) Kafka may fail to connect to ZooKeeper, retry forever, and never start

[ https://issues.apache.org/jira/browse/KAFKA-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13270: -- Description: The implementation of https://issues.apache.org/jira/browse/ZOOKEEPER-3593 in

[jira] [Created] (KAFKA-13270) Kafka may fail to connect to ZooKeeper, retry forever, and never start

Ron Dagostino created KAFKA-13270: - Summary: Kafka may fail to connect to ZooKeeper, retry forever, and never start Key: KAFKA-13270 URL: https://issues.apache.org/jira/browse/KAFKA-13270 Project:

[jira] [Created] (KAFKA-13224) broker.id does not appear in config's originals map when setting just node.id

Ron Dagostino created KAFKA-13224: - Summary: broker.id does not appear in config's originals map when setting just node.id Key: KAFKA-13224 URL: https://issues.apache.org/jira/browse/KAFKA-13224

[jira] [Updated] (KAFKA-13219) BrokerState metric not working for KRaft clusters

[ https://issues.apache.org/jira/browse/KAFKA-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13219: -- Priority: Blocker (was: Major) > BrokerState metric not working for KRaft clusters >

[jira] [Updated] (KAFKA-13219) BrokerState metric not working for KRaft clusters

[ https://issues.apache.org/jira/browse/KAFKA-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13219: -- Fix Version/s: 3.0.0 > BrokerState metric not working for KRaft clusters >

[jira] [Created] (KAFKA-13219) BrokerState metric not working for KRaft clusters

Ron Dagostino created KAFKA-13219: - Summary: BrokerState metric not working for KRaft clusters Key: KAFKA-13219 URL: https://issues.apache.org/jira/browse/KAFKA-13219 Project: Kafka Issue

[jira] [Assigned] (KAFKA-13192) broker.id and node.id can be specified inconsistently

[ https://issues.apache.org/jira/browse/KAFKA-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino reassigned KAFKA-13192: - Assignee: Ron Dagostino > broker.id and node.id can be specified inconsistently >

[jira] [Created] (KAFKA-13192) broker.id and node.id can be specified inconsistently

Ron Dagostino created KAFKA-13192: - Summary: broker.id and node.id can be specified inconsistently Key: KAFKA-13192 URL: https://issues.apache.org/jira/browse/KAFKA-13192 Project: Kafka

[jira] [Created] (KAFKA-13140) KRaft brokers do not expose kafka.controller metrics, breaking backwards compatibility

Ron Dagostino created KAFKA-13140: - Summary: KRaft brokers do not expose kafka.controller metrics, breaking backwards compatibility Key: KAFKA-13140 URL: https://issues.apache.org/jira/browse/KAFKA-13140

[jira] [Created] (KAFKA-13137) KRaft Controller Metric MBean names are incorrectly quoted

Ron Dagostino created KAFKA-13137: - Summary: KRaft Controller Metric MBean names are incorrectly quoted Key: KAFKA-13137 URL: https://issues.apache.org/jira/browse/KAFKA-13137 Project: Kafka

[jira] [Resolved] (KAFKA-13069) Add magic number to DefaultKafkaPrincipalBuilder.KafkaPrincipalSerde

[ https://issues.apache.org/jira/browse/KAFKA-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino resolved KAFKA-13069. --- Resolution: Invalid Flexible fields are sufficient as per KIP-590 VOTE email thread, so a

[jira] [Commented] (KAFKA-13069) Add magic number to DefaultKafkaPrincipalBuilder.KafkaPrincipalSerde

[ https://issues.apache.org/jira/browse/KAFKA-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380097#comment-17380097 ] Ron Dagostino commented on KAFKA-13069: --- See email sent to KIP-590 VOTE thread about this issue.

[jira] [Updated] (KAFKA-13069) Add magic number to DefaultKafkaPrincipalBuilder.KafkaPrincipalSerde

[ https://issues.apache.org/jira/browse/KAFKA-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-13069: -- Priority: Critical (was: Major) > Add magic number to

[jira] [Created] (KAFKA-13069) Add magic number to DefaultKafkaPrincipalBuilder.KafkaPrincipalSerde

Ron Dagostino created KAFKA-13069: - Summary: Add magic number to DefaultKafkaPrincipalBuilder.KafkaPrincipalSerde Key: KAFKA-13069 URL: https://issues.apache.org/jira/browse/KAFKA-13069 Project:

[jira] [Commented] (KAFKA-12946) __consumer_offsets topic with very big partitions

[ https://issues.apache.org/jira/browse/KAFKA-12946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363805#comment-17363805 ] Ron Dagostino commented on KAFKA-12946: --- The only one I am familiar with and would recommend is

[jira] [Commented] (KAFKA-12946) __consumer_offsets topic with very big partitions

[ https://issues.apache.org/jira/browse/KAFKA-12946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363584#comment-17363584 ] Ron Dagostino commented on KAFKA-12946: --- Yeah, there are bugs. The KIP I referred to mentions

[jira] [Commented] (KAFKA-12946) __consumer_offsets topic with very big partitions

[ https://issues.apache.org/jira/browse/KAFKA-12946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363496#comment-17363496 ] Ron Dagostino commented on KAFKA-12946: --- I mean if you take a look at the size on disk, is the

[jira] [Commented] (KAFKA-12946) __consumer_offsets topic with very big partitions

[ https://issues.apache.org/jira/browse/KAFKA-12946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363155#comment-17363155 ] Ron Dagostino commented on KAFKA-12946: --- If the partition isn't being cleaned then you can try

[jira] [Updated] (KAFKA-12897) KRaft Controller cannot create topic with multiple partitions on a single broker cluster

[ https://issues.apache.org/jira/browse/KAFKA-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-12897: -- Description: https://github.com/apache/kafka/pull/10494 introduced a bug in the KRaft

[jira] [Updated] (KAFKA-12897) KRaft Controller cannot create topic with multiple partitions on a single broker cluster

[ https://issues.apache.org/jira/browse/KAFKA-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-12897: -- Summary: KRaft Controller cannot create topic with multiple partitions on a single broker

[jira] [Updated] (KAFKA-12897) KRaft Controller cannot create topic with replication factor greater than number of racks

[ https://issues.apache.org/jira/browse/KAFKA-12897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ron Dagostino updated KAFKA-12897: -- Description: https://github.com/apache/kafka/pull/10494 introduced a bug in the KRaft

  1   2   >