You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/29 20:30:20 UTC
[jira] [Commented] (BOOKKEEPER-945) Add counters to track the
activity of auditor and replication workers
[ https://issues.apache.org/jira/browse/BOOKKEEPER-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446966#comment-15446966 ]
ASF GitHub Bot commented on BOOKKEEPER-945:
-------------------------------------------
GitHub user rithin-shetty opened a pull request:
https://github.com/apache/bookkeeper/pull/57
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rithin-shetty/bookkeeper auto_recovery_counters
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/57.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #57
----
commit 90d6879336c6c3f47a02152ed97e87b7c9fa340e
Author: Rithin <ri...@salesforce.com>
Date: 2016-08-29T20:23:24Z
BOOKKEEPER-945 Add counters to track the activity of auditor and replication 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.
----
> 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)