[
https://issues.apache.org/jira/browse/KAFKA-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
José Armando García Sancio updated KAFKA-19108:
-----------------------------------------------
Description:
The kafka-metadata-quorum describe tool prints the zero UUID the controller
cluster is statically configured.
{code:java}
kafka-metadata-quorum --bootstrap-server ... describe --replication
NodeId DirectoryId LogEndOffset Lag LastFetchTimestamp
LastCaughtUpTimestamp Status
2 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446547
1743659446547 Leader
1 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446184
1743659446184 Follower
3 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446184
1743659446184 Follower
1002 5vgiCabs9tK9OPvBRIdDDA 44871305 0 1743659446183
1743659446183 Observer
1001 Ar8bDr3xvE5biu8dzZyWJg 44871305 0 1743659446183
1743659446183 Observer
1003 _PzCB3U28DKYkW3QkY_Clg 44871305 0 1743659446183
1743659446183 Observer {code}
It does this because for static controllers there is no directory id in the
voter set. The leader knows the voters directory id because it is included in
the FETCH request. Consider storing this information in the leader's in-memory
state and printing it when requesting the replication status.
was:
The kafka-metadata-quorum describe tool prints the zero UUID the controller
cluster is statically configured.
{code:java}
kafka-metadata-quorum --bootstrap-server ... describe --replication
NodeId DirectoryId LogEndOffset Lag LastFetchTimestamp
LastCaughtUpTimestamp Status
2 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446547
1743659446547 Leader
1 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446184
1743659446184 Follower
3 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446184
1743659446184 Follower
1002 5vgiCabs9tK9OPvBRIdDDA 44871305 0 1743659446183
1743659446183 Observer
1001 Ar8bDr3xvE5biu8dzZyWJg 44871305 0 1743659446183
1743659446183 Observer
1003 _PzCB3U28DKYkW3QkY_Clg 44871305 0 1743659446183
1743659446183 Observer {code}
It doesn this because for static controllers there is no directory id in the
voter set. The leader knows the voters directory id because it is included in
the FETCH request. Consider storing this information in the leader's in-memory
state and printing it when requesting the replication status.
> Consider improving the UI when describing static voters
> -------------------------------------------------------
>
> Key: KAFKA-19108
> URL: https://issues.apache.org/jira/browse/KAFKA-19108
> Project: Kafka
> Issue Type: Sub-task
> Components: kraft
> Affects Versions: 3.9.0
> Reporter: José Armando García Sancio
> Assignee: José Armando García Sancio
> Priority: Minor
>
> The kafka-metadata-quorum describe tool prints the zero UUID the controller
> cluster is statically configured.
> {code:java}
> kafka-metadata-quorum --bootstrap-server ... describe --replication
> NodeId DirectoryId LogEndOffset Lag LastFetchTimestamp
> LastCaughtUpTimestamp Status
> 2 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446547
> 1743659446547 Leader
> 1 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446184
> 1743659446184 Follower
> 3 AAAAAAAAAAAAAAAAAAAAAA 44871305 0 1743659446184
> 1743659446184 Follower
> 1002 5vgiCabs9tK9OPvBRIdDDA 44871305 0 1743659446183
> 1743659446183 Observer
> 1001 Ar8bDr3xvE5biu8dzZyWJg 44871305 0 1743659446183
> 1743659446183 Observer
> 1003 _PzCB3U28DKYkW3QkY_Clg 44871305 0 1743659446183
> 1743659446183 Observer {code}
> It does this because for static controllers there is no directory id in the
> voter set. The leader knows the voters directory id because it is included in
> the FETCH request. Consider storing this information in the leader's
> in-memory state and printing it when requesting the replication status.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
