[
https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098979#comment-14098979
]
Rakesh R commented on BOOKKEEPER-736:
-------------------------------------
bq. the stats of re-replication already gives what you want.
Are you pointing me to
rereplicateOpStats.registerSuccessfulEvent(latencyMillis);. Does this gives
NumRereplicatedLedgers ?
If I'm wrong please point me to the correct one. Thanks.
bq. as I said, the only place that have total number of under replicated
ledgers in the bk cluster is the zookeeper metadata. the counter that you have
just indicated that under replicated ledgers that the bookie process found
during it is running. it doest provide any useful info.
If there are UrLedgers it gives hint that the BK cluster has to be carefully
observed to see its successful recovery, because there are missing replicas and
could be a concern for critical data like Namenode WAL. I agree there is an
alternative path by just querying through bookie shell command
"listunderreplicated". But I'm trying to see any possibilities of exposing it
as stats.
> Stats for AutoRecovery
> ----------------------
>
> Key: BOOKKEEPER-736
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-auto-recovery
> Reporter: Rakesh R
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-736.patch, BOOKKEEPER-736.v2.patch,
> Prototype-JMX-beans-for-standalone-autorecovery-process.png
>
>
> Idea of this JIRA is to provide jmx interfaces to get the statistics of the
> auto recovery activities.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
