[
https://issues.apache.org/jira/browse/HBASE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans updated HBASE-2838:
--------------------------------------
Fix Version/s: 0.90.0
Description:
Replication needs to publish metrics about its performance:
- WALEdits read, filtered, sent to slave clusters, applied on slaves
- size of batches sent/received
- ms spent on reading, sending, applying edits
This can be done using HadoopMetrics.
Also we need to publish information not related to performance:
- size of each HLog queues
- age of the last replicated edit in each queue
- time of last successful replication
These informations can hardly be graphed, but we still need to represent them
somehow. It has to be accessible by web UI, shell, and other tools in general.
I don't feel strongly about creating a new public method on HRS's interface,
and I'm not sure publishing those in ZooKeeper is a good idea either (why add
another indirection?). Still wondering about a better solution.
> Replication metrics
> -------------------
>
> Key: HBASE-2838
> URL: https://issues.apache.org/jira/browse/HBASE-2838
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.90.0
>
>
> Replication needs to publish metrics about its performance:
> - WALEdits read, filtered, sent to slave clusters, applied on slaves
> - size of batches sent/received
> - ms spent on reading, sending, applying edits
> This can be done using HadoopMetrics.
> Also we need to publish information not related to performance:
> - size of each HLog queues
> - age of the last replicated edit in each queue
> - time of last successful replication
> These informations can hardly be graphed, but we still need to represent them
> somehow. It has to be accessible by web UI, shell, and other tools in
> general. I don't feel strongly about creating a new public method on HRS's
> interface, and I'm not sure publishing those in ZooKeeper is a good idea
> either (why add another indirection?). Still wondering about a better
> solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
