[jira] [Commented] (KAFKA-9125) GroupMetadataManager and TransactionStateManager should query the controller instead of zkClient

2021-04-17 Thread Colin McCabe (Jira) 


[ 
https://issues.apache.org/jira/browse/KAFKA-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324369#comment-17324369
 ] 

Colin McCabe commented on KAFKA-9125:
-

We do indeed now get GroupMetadataManager and TransactionStateManager metadata 
from the metadata topic (and associated cache) when in KRaft (kip-500) mode.  
Closing as fixed.

> GroupMetadataManager and TransactionStateManager should query the controller 
> instead of zkClient
> 
>
> Key: KAFKA-9125
> URL: https://issues.apache.org/jira/browse/KAFKA-9125
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Viktor Somogyi-Vass
>Assignee: Viktor Somogyi-Vass
>Priority: Major
>
> Both classes query their respective topic's partition count via the zkClient. 
> This however could be queried by the broker's local metadata cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (KAFKA-9125) GroupMetadataManager and TransactionStateManager should query the controller instead of zkClient

2019-12-12 Thread ErKang QI (Jira) 


[ 
https://issues.apache.org/jira/browse/KAFKA-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994552#comment-16994552
 ] 

ErKang QI commented on KAFKA-9125:
--

mark (*)

> GroupMetadataManager and TransactionStateManager should query the controller 
> instead of zkClient
> 
>
> Key: KAFKA-9125
> URL: https://issues.apache.org/jira/browse/KAFKA-9125
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Viktor Somogyi-Vass
>Assignee: Viktor Somogyi-Vass
>Priority: Major
>
> Both classes query their respective topic's partition count via the zkClient. 
> This however could be queried by the broker's local metadata cache.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)