hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2888) Review all our metrics
Date Wed, 24 Nov 2010 03:57:14 GMT

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

stack commented on HBASE-2888:
------------------------------

@Alex 1. and 2. sound great.  How would 3. differ from current log?  All it has in it is 'events',
no?  Regards your question about process, I'd say no need of an issue per metric., at least
not for now.  The way it usually runs is we have a fat umbrella issue like this one, a bunch
of work gets done under this umbrella -- in this case, a bunch of the above will be addressed
by the patch -- but then subsequent amendments or additions get done in separate issues. 
Hope this helps.

> Review all our metrics
> ----------------------
>
>                 Key: HBASE-2888
>                 URL: https://issues.apache.org/jira/browse/HBASE-2888
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.92.0
>
>
> HBase publishes a bunch of metrics, some useful some wasteful, that should be improved
to deliver a better ops experience. Examples:
>  - Block cache hit ratio converges at some point and stops moving
>  - fsReadLatency goes down when compactions are running
>  - storefileIndexSizeMB is the exact same number once a system is serving production
load
> We could use new metrics too.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message