[
https://issues.apache.org/jira/browse/BOOKKEEPER-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sijie Guo resolved BOOKKEEPER-945.
----------------------------------
Resolution: Fixed
Issue resolved by merging pull request 57
[https://github.com/apache/bookkeeper/pull/57]
{noformat}
commit 9dc05fc080ddf01e69eb89ce1b0865c552d3de53
Author: Rithin <[email protected]>
AuthorDate: Sat Sep 10 12:01:27 2016 -0700
Commit: Sijie Guo <[email protected]>
CommitDate: Sat Sep 10 12:01:27 2016 -0700
BOOKKEEPER-945: Add counters to track the activity of auditor and repl…
…ication workers
Once we enable auto recovery, auditor and replication workers start their
activity.
Today there is no way to monitor it using counters. This change introduces
the
following counters to track various activities of auditor and replication
workers like:
- Time taken by auditor to build the bookie->ledger list
- No. of under replicated ledgers detected
- Time taken by auditor to publish the under replicated ledger list
- Time taken by auditor to check all the ledgers in the cluster
- No. of ledgers replicated by each replication worker
- No. of entries and bytes of data read and written by each replication
worker
- Auditor can also report the distribution of ledgers within the cluster:
how many bookies own a piece of ledger, etc.
Author: Rithin <[email protected]>
Reviewers: [email protected] <[email protected]>
Closes #57 from rithin-shetty/auto_recovery_counters
{noformat}
> Add counters to track the activity of auditor and replication workers
> ---------------------------------------------------------------------
>
> Key: BOOKKEEPER-945
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-945
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Affects Versions: 4.5.0
> Reporter: Rithin Shetty
> Assignee: Rithin Shetty
> Priority: Minor
> Fix For: 4.5.0
>
>
> Once we enable auto recovery, auditor and replication workers start their
> activity. Today there is no way to monitor it using counters. This is a bug
> to track various activities of auditor and replication workers like:
> - Time taken by auditor to build the bookie->ledger list
> - No. of under replicated ledgers detected
> - Time taken by auditor to publish the under replicated ledger list
> - Time taken by auditor to check all the ledgers in the cluster
> - No. of ledgers replicated by each replication worker
> - No. of entries and bytes of data read and written by each replication worker
> - Auditor can also report the distribution of ledgers within the cluster: how
> many bookies own a piece of ledger, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
