You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Federico Valeri (Jira)" <ji...@apache.org> on 2023/05/21 08:50:00 UTC
[jira] [Commented] (KAFKA-14982) Improve the kafka-metadata-quorum output
[ https://issues.apache.org/jira/browse/KAFKA-14982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724600#comment-17724600 ]
Federico Valeri commented on KAFKA-14982:
-----------------------------------------
https://cwiki.apache.org/confluence/display/KAFKA/KIP-927%3A+Improve+the+kafka-metadata-quorum+output
> Improve the kafka-metadata-quorum output
> ----------------------------------------
>
> Key: KAFKA-14982
> URL: https://issues.apache.org/jira/browse/KAFKA-14982
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 3.5.0
> Reporter: Luke Chen
> Assignee: Federico Valeri
> Priority: Major
> Labels: need-kip
> Fix For: 3.6.0
>
>
> When running kafka-metadata-quorum script to get the quorum replication status, I found the LastFetchTimestamp and LastCaughtUpTimestamp output is not human readable. The timestamp 1683701749161 is just a random integer to me. We should convert it into date/time (ex: May 10, 08:00 UTC), or if possible, convert it into strings like "10 seconds ago", "5 minutes ago"...
>
>
> {code:java}
> % ./bin/kafka-metadata-quorum.sh --bootstrap-server localhost:9092 describe --replication
> NodeId LogEndOffset Lag LastFetchTimestamp LastCaughtUpTimestamp Status
> 1 166 0 1683701749161 1683701749161 Leader
> 6 166 0 1683701748776 1683701748776 Follower
> 7 166 0 1683701748773 1683701748773 Follower
> 2 166 0 1683701748766 1683701748766 Observer {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)