hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5434) [REST] Include more metrics in cluster status request
Date Wed, 21 Mar 2012 21:26:35 GMT

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

Hadoop QA commented on HBASE-5434:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    -1 findbugs.  The patch appears to introduce 3 new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

     -1 core tests.  The patch failed these unit tests:

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1241//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1241//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1241//console

This message is automatically generated.
> [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, HBASE-5434.trunk.v2.patch, HBASE-5434.trunk.v2.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