[
https://issues.apache.org/jira/browse/HBASE-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564241#comment-15564241
]
stack commented on HBASE-16800:
-------------------------------
>From a server @appy put up w/ replication running:
{code}
{
"beans" : [ {
"name" : "Hadoop:service=HBase,name=RegionServer,sub=Replication",
"modelerType" : "RegionServer,sub=Replication",
"tag.Context" : "regionserver",
"tag.Hostname" : "ve0206.halxg.cloudera.com",
"source.1.shippedOps" : 3,
"source.shippedKBs" : 0,
"source.1.shippedBatches" : 3,
"source.sizeOfLogQueue" : 3,
"source.logEditsFiltered" : 2,
"source.1.shippedKBs" : 0,
"source.1.ageOfLastShippedOp" : 1657226,
"source.1.logReadInBytes" : 969,
"source.logReadInBytes" : 969,
"source.1.logEditsRead" : 6,
"sink.appliedOps" : 0,
"source.1.sizeOfLogQueue" : 3,
"source.shippedOps" : 3,
"source.logEditsRead" : 6,
"source.shippedBatches" : 3,
"sink.ageOfLastAppliedOp" : 0,
"source.ageOfLastShippedOp" : 1657226,
"source.1.logEditsFiltered" : 2,
"sink.appliedBatches" : 0
} ]
}
{code}
Seems like we want the whole bean to tell the replication story so in this case
the qry by mbean as @appy says is good enough.
If we need more fine-grained querying, searching, listing, compression, batch,
etc., then we can come back here to this patch that adds jolokai. Meantime I've
made the issue minor.
Also, we were going to bring in jolokai -- another dependency -- it'd be good
to replace our current jmx servlet with it instead.
> Support for smart querying of our published jmx per server over http+json
> -------------------------------------------------------------------------
>
> Key: HBASE-16800
> URL: https://issues.apache.org/jira/browse/HBASE-16800
> Project: HBase
> Issue Type: Improvement
> Components: metrics
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Attachments: HBASE-16800.master.001.patch,
> HBASE-16800.master.002.patch
>
>
> We currently expose our jmx metrics via a json dump in a servlet at /jmx. You
> get all or nothing (You can add a '?description=true' to get a description
> for each metric published but that is it).
> A means of being able to query by metric or by a set of metrics would make
> graphing easier to do, especially over http dumping json. In particular, our
> [~appy] is trying to put up pages that give insight into current state of
> replication.
> Related, HBASE-11747 ClusterStatus is too bulky, is about how whenever we
> need a metric 'exposed', our only means is by bulking out the heartbeat
> adding payload on each message we send the server (In the issue, w/ 1M
> regions, each RS is sending 100MB of 'status' every second). We need to undo
> metrics collection from clusterstatus function
> Bonus if able to compress/cache payloads, security, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
