hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5434) [REST] Include more metrics in cluster status request
Date Thu, 23 Feb 2012 19:02:50 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214940#comment-13214940

Andrew Purtell commented on HBASE-5434:

Check exactly what is being checked at  {{{TestStorageClusterStatusModel.checkModel(TestStorageClusterStatusModel.java:126)}}}

When checking cluster status, if there's some race or nondeterministic behavior in the test
rig, for example sometimes a RS takes a long time to spin up on Hudson but not locally, then
that can fail the test.

IMO, it might be best to fully mock the cluster status model so the above is no longer an
(occasional) concern.
> [REST] Include more metrics in cluster status request
> -----------------------------------------------------
>                 Key: HBASE-5434
>                 URL: https://issues.apache.org/jira/browse/HBASE-5434
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics, rest
>    Affects Versions: 0.94.0
>            Reporter: Mubarak Seyed
>            Assignee: Mubarak Seyed
>            Priority: Minor
>              Labels: noob
>             Fix For: 0.94.0
>         Attachments: HBASE-5434.trunk.v1.patch
> /status/cluster shows only
> {code}
> stores=2
> storefiless=0
> storefileSizeMB=0
> memstoreSizeMB=0
> storefileIndexSizeMB=0
> {code}
> for a region but master web-ui shows
> {code}
> stores=1,
> storefiles=0,
> storefileUncompressedSizeMB=0
> storefileSizeMB=0
> memstoreSizeMB=0
> storefileIndexSizeMB=0
> readRequestsCount=0
> writeRequestsCount=0
> rootIndexSizeKB=0
> totalStaticIndexSizeKB=0
> totalStaticBloomSizeKB=0
> totalCompactingKVs=0
> currentCompactedKVs=0
> compactionProgressPct=NaN
> {code}
> In a write-heavy REST gateway based production environment, ops team needs to verify
whether write counters are getting incremented per region (they do run /status/cluster on
each REST server), we can get the same values from *rpc.metrics.put_num_ops* and *hbase.regionserver.writeRequestsCount*
but some home-grown tools needs to parse the output of /status/cluster and updates the dashboard.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message