Hi, I have some questions about motivation. The problem to be solved by this kip is that it cannot accurately monitor the topic and group currently being replicated? From my point of view, using MirrorSourceMetrics.recordRate can monitor the configured topic list that is currently being replicated (even if the topic has no data), and using MirrorCheckpointMetrics.CHECKPOINT_LATENCY can monitor the currently replicated group list (if it is wrong, please correct me).
best, hudeqi "Dániel Urbán" <urb.dani...@gmail.com>写道： > Hello everyone, > > I would like to bump this KIP. Please consider reviewing it, as it would > improve the monitoring capabilities around MM2. > I also submitted a PR (https://github.com/apache/kafka/pull/13595) to > demonstrate the current state of the KIP. > > Thanks in advance, > Daniel > > Dániel Urbán <urb.dani...@gmail.com> ezt írta (időpont: 2023. ápr. 13., Cs, > 15:02): > > > Hi everyone, > > > > I would like to start a discussion on KIP-918: MM2 Topic And Group > > Listener ( > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-918%3A+MM2+Topic+And+Group+Listener > > ). > > This new feature of MM2 would allow following the latest set of replicated > > topics and groups, which is currently not possible in MM2. Additionally, > > this would help IdentityReplicationPolicy users, as they could use this new > > feature to track the replicated topics (which is not available through the > > policy due to topics not being renamed during replication). > > > > Thanks in advance, > > Daniel > >
