You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mubarak Seyed (Created) (JIRA)" <ji...@apache.org> on 2012/02/19 03:05:59 UTC
[jira] [Created] (HBASE-5434) [REST] Include more metrics in
cluster status request
[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
Fix For: 0.94.0
/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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237702#comment-13237702 ]
Hudson commented on HBASE-5434:
-------------------------------
Integrated in HBase-0.94 #53 (See [https://builds.apache.org/job/HBase-0.94/53/])
HBASE-5434 [REST] Include more metrics in cluster status request (Mubarak Seyed) (Revision 1304918)
Result = SUCCESS
larsh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/HServerLoad.java
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/rest/StorageClusterStatusResource.java
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterStatusModel.java
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/rest/protobuf/generated/StorageClusterStatusMessage.java
* /hbase/branches/0.94/src/main/resources/org/apache/hadoop/hbase/rest/XMLSchema.xsd
* /hbase/branches/0.94/src/main/resources/org/apache/hadoop/hbase/rest/protobuf/StorageClusterStatusMessage.proto
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterStatusModel.java
> [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, 0.96.0
>
> Attachments: HBASE-5434.trunk.v1.patch, HBASE-5434.trunk.v2.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
[jira] [Issue Comment Edited] (HBASE-5434) [REST] Include more
metrics in cluster status request
Posted by "Andrew Purtell (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211222#comment-13211222 ]
Andrew Purtell edited comment on HBASE-5434 at 2/19/12 6:17 AM:
----------------------------------------------------------------
+1
The cluster status representation hasn't been updated since 0.90.
was (Author: apurtell):
+1
Te cluster status representation hasn't been updated since 0.90.
> [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
>
>
> /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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214357#comment-13214357 ]
stack commented on HBASE-5434:
------------------------------
It fails on hadoopqa too...
{code}
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.rest.model.TestStorageClusterStatusModel
{code}
Does it fail for you Mubarak?
> [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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Status: Open (was: Patch Available)
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238043#comment-13238043 ]
Hudson commented on HBASE-5434:
-------------------------------
Integrated in HBase-TRUNK #2695 (See [https://builds.apache.org/job/HBase-TRUNK/2695/])
HBASE-5434 [REST] Include more metrics in cluster status request (Mubarak Seyed) (Revision 1304919)
Result = FAILURE
larsh :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/HServerLoad.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/rest/StorageClusterStatusResource.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterStatusModel.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/rest/protobuf/generated/StorageClusterStatusMessage.java
* /hbase/trunk/src/main/resources/org/apache/hadoop/hbase/rest/XMLSchema.xsd
* /hbase/trunk/src/main/resources/org/apache/hadoop/hbase/rest/protobuf/StorageClusterStatusMessage.proto
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterStatusModel.java
> [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, 0.96.0
>
> Attachments: HBASE-5434.trunk.v1.patch, HBASE-5434.trunk.v2.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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Andrew Purtell (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Lars Hofhansl (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-5434:
---------------------------------
Resolution: Fixed
Fix Version/s: 0.96.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to 0.94 and 0.96.
> [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, 0.96.0
>
> Attachments: HBASE-5434.trunk.v1.patch, HBASE-5434.trunk.v2.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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237677#comment-13237677 ]
stack commented on HBASE-5434:
------------------------------
+1 on commit
> [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, 0.96.0
>
> Attachments: HBASE-5434.trunk.v1.patch, HBASE-5434.trunk.v2.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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Status: Patch Available (was: Open)
Submit Mubaraks' new patch
> [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
>
>
> /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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Andrew Purtell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214041#comment-13214041 ]
Andrew Purtell commented on HBASE-5434:
---------------------------------------
+1
Looks good Mubarak.
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213897#comment-13213897 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
Need to update schema definition in wiki page http://wiki.apache.org/hadoop/Hbase/Stargate
*protobufs schema*
{code}
message StorageClusterStatus {
message Region {
required bytes name = 1;
optional int32 stores = 2;
optional int32 storefiles = 3;
optional int32 storefileSizeMB = 4;
optional int32 memstoreSizeMB = 5;
optional int32 storefileIndexSizeMB = 6;
optional int64 readRequestsCount = 7;
optional int64 writeRequestsCount = 8;
optional int32 rootIndexSizeKB = 9;
optional int32 totalStaticIndexSizeKB = 10;
optional int32 totalStaticBloomSizeKB = 11;
optional int64 totalCompactingKVs = 12;
optional int64 currentCompactedKVs = 13;
{color}
}
..
}
{code}
*XML schema*
{code}
<complexType name="Region">
<attribute name="name" type="base64Binary"></attribute>
<attribute name="stores" type="int"></attribute>
<attribute name="storefiles" type="int"></attribute>
<attribute name="storefileSizeMB" type="int"></attribute>
<attribute name="memstoreSizeMB" type="int"></attribute>
<attribute name="storefileIndexSizeMB" type="int"></attribute>
<attribute name="readRequestsCount" type="int"></attribute>
<attribute name="writeRequestsCount" type="int"></attribute>
<attribute name="rootIndexSizeKB" type="int"></attribute>
<attribute name="totalStaticIndexSizeKB" type="int"></attribute>
<attribute name="totalStaticBloomSizeKB" type="int"></attribute>
<attribute name="totalCompactingKVs" type="int"></attribute>
<attribute name="currentCompactedKVs" type="int"></attribute>
</complexType>
{code}
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Andrew Purtell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211222#comment-13211222 ]
Andrew Purtell commented on HBASE-5434:
---------------------------------------
+1
Te cluster status representation hasn't been updated since 0.90.
> [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
>
>
> /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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mubarak Seyed updated HBASE-5434:
---------------------------------
Attachment: HBASE-5434.trunk.v2.patch
The attached file is an updated patch (with fix for unit test failure)
There was an incorrect Protobuf base64 encoded string
{code}
- private static final String AS_PB =
-"Ci0KBXRlc3QxEOO6i+eeJBgAIIABKIAIMhUKCS1ST09ULSwsMBABGAEgACgAMAAKOQoFdGVzdDIQ"+
-"/pKx8J4kGAAggAQogAgyIQoVLk1FVEEuLCwxMjQ2MDAwMDQzNzI0EAEYASAAKAAwABgCIAApAAAA"+
-"AAAA8D8=";
-
+ private static final String AS_PB =
+ "CjsKBXRlc3QxEOO6i+eeJBgAIIABKIAIMiMKCS1ST09ULSwsMBABGAEgACgAMAA4AUACSAFQAVgB" +
+ "YAFoAQpHCgV0ZXN0MhD+krHwniQYACCABCiACDIvChUuTUVUQS4sLDEyNDYwMDAwNDM3MjQQARgB" +
+ "IAAoADAAOAFAAkgBUAFYAWABaAEYAiAAKQAAAAAAAPA/";
{code}
Unit tested all the rest test code.
{code}
mvn -e -up clean test - Dtest=org.apache.hadoop.hbase.rest.*
Results :
Tests run: 51, Failures: 0, Errors: 0, Skipped: 0
{code}
Sorry for the inconvenience. Thanks.
> [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
>
>
> /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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214355#comment-13214355 ]
Hadoop QA commented on HBASE-5434:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12515296/HBASE-5434.trunk.v1.patch
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 appears to have generated -136 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 152 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.rest.model.TestStorageClusterStatusModel
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1019//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1019//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1019//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
>
>
> /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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Status: Open (was: Patch Available)
> [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
>
>
> /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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mubarak Seyed updated HBASE-5434:
---------------------------------
Attachment: HBASE-5434.trunk.v1.patch
The attached file is a patch.
Unit tests are passed. Tested in 5 node dev cluster. Thanks.
> [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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Status: Patch Available (was: Open)
> [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, 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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ 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
http://issues.apache.org/jira/secure/attachment/12519299/HBASE-5434.trunk.v2.patch
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 warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestImportTsv
org.apache.hadoop.hbase.mapred.TestTableMapReduce
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
org.apache.hadoop.hbase.master.TestSplitLogManager
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, 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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215269#comment-13215269 ]
Hadoop QA commented on HBASE-5434:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12515849/HBASE-5434.trunk.v2.patch
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 appears to have generated -136 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 152 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.coprocessor.TestClassLoading
org.apache.hadoop.hbase.regionserver.TestStore
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1034//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1034//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1034//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
>
>
> /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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213905#comment-13213905 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
@Andrew
Can you please review the patch? Thanks.
> [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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Attachment: HBASE-5434.trunk.v2.patch
Reupload of Mubarak's last patch to run it by hadoopqa again
> [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, 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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214145#comment-13214145 ]
stack commented on HBASE-5434:
------------------------------
I added you Mubarak. Try editing wiki (I'm in process of applying this patch).
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214945#comment-13214945 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
@Stack
When i tested with -P runMediumTests, it went well but code annotate as smallTests, will update a patch soon. Sorry for the inconvenience. Thanks.
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214116#comment-13214116 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
@Stack
My wiki id is "Mubarak Seyed". Thanks
> [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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Attachment: HBASE-5434.trunk.v2.patch
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214114#comment-13214114 ]
stack commented on HBASE-5434:
------------------------------
@Mubarak What is your wiki id and I'll add you as a contributor
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213878#comment-13213878 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
Could not get _compactionProgressPct_ value as it depends on [HBASE-3943|https://issues.apache.org/jira/browse/HBASE-3943], so _compactionProgressPct_ will not be included in output. Thanks.
> [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
[jira] [Updated] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5434:
-------------------------
Status: Patch Available (was: Open)
Submitting patch because when I tried it local I got this:
{code}
Failed tests: testFromXML(org.apache.hadoop.hbase.rest.model.TestStorageClusterStatusModel): expected:<0> but was:<1>
testFromPB(org.apache.hadoop.hbase.rest.model.TestStorageClusterStatusModel): expected:<0> but was:<1>
{code}
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234946#comment-13234946 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
Test failure @24/Feb/12 00:35 are not related to the patch.
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Mubarak Seyed (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214051#comment-13214051 ]
Mubarak Seyed commented on HBASE-5434:
--------------------------------------
Thanks Andrew.
@Ted.
Can you please take care of updating the wiki page once it is committed as i don't have an access? Thanks.
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Lars Hofhansl (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234911#comment-13234911 ]
Lars Hofhansl commented on HBASE-5434:
--------------------------------------
Is this ready for 0.94?
> [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
[jira] [Commented] (HBASE-5434) [REST] Include more metrics in
cluster status request
Posted by "Lars Hofhansl (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237443#comment-13237443 ]
Lars Hofhansl commented on HBASE-5434:
--------------------------------------
Anybody opposed to committing this?
> [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, 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