> Hello Niket, currently DescribeQuorumResponse is not a public API, we don’t have a Admin api or shell script to get DescribeQuorumResponse, so it’s unnecessary to submit a KIP to change it, you can just submit a PR to accomplish this.
Hey Ziming, I think it is public. It was documented in KIP-595 and we have implemented the API on the server. However, it looks like I never added the Admin API (even though it is assumed by the `kafka-metadata-quorum.sh` tool). @Niket does it make sense to add the Admin API to this KIP? Best, Jason On Mon, May 9, 2022 at 8:09 PM deng ziming <dengziming1...@gmail.com> wrote: > Hello Niket, currently DescribeQuorumResponse is not a public API, we > don’t have a Admin api or shell script to get DescribeQuorumResponse, so > it’s unnecessary to submit a KIP to change it, you can just submit a PR to > accomplish this. > > -- > Thanks > Ziming > > > On May 10, 2022, at 1:33 AM, Niket Goel <ng...@confluent.io.INVALID> > wrote: > > > > Hi all, > > > > I created a KIP to add some more information to > `DesscribeQuorumResponse` to enable ascertaining voter lag in the quorum a > little better. > > Please see KIP -- > https://cwiki.apache.org/confluence/display/KAFKA/KIP-836%3A+Additional+Information+in+DescribeQuorumResponse+about+Voter+Lag > > > > Thanks for your feedback, > > Niket Goel > >
