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

Enis Soztutar commented on HBASE-15464:
---------------------------------------

Here is what we have today. 
Per regionserver flush metrics: 
{code}
    "flushQueueLength" : 0,
    "flushedCellsCount" : 684,
    "flushedCellsSize" : 109440,
    "FlushTime_num_ops" : 60,
    "FlushTime_min" : 9223372036854775807,
    "FlushTime_max" : 0,
    "FlushTime_mean" : 0,
    "FlushTime_25th_percentile" : 0,
    "FlushTime_median" : 0,
    "FlushTime_75th_percentile" : 0,
    "FlushTime_90th_percentile" : 0,
    "FlushTime_95th_percentile" : 0,
    "FlushTime_98th_percentile" : 0,
    "FlushTime_99th_percentile" : 0,
    "FlushTime_99.9th_percentile" : 0,
{code}

Per-region, we don't have flush metrics. 


Per regionserver compaction metrics:
{code}
    "compactionQueueLength" : 0,
    "compactedCellsCount" : 357,
    "majorCompactedCellsCount" : 124,
    "compactedCellsSize" : 162279544,
    "majorCompactedCellsSize" : 0,
{code}

Per region compaction metrics:
{code}
    
"Namespace_hbase_table_meta_region_1588230740_metric_compactionsCompletedCount" 
: 3,
    
"Namespace_hbase_table_meta_region_1588230740_metric_numBytesCompactedCount" : 
91549,
    
"Namespace_hbase_table_meta_region_1588230740_metric_numFilesCompactedCount" : 
9,
{code}



> Flush / Compaction metrics revisited
> ------------------------------------
>
>                 Key: HBASE-15464
>                 URL: https://issues.apache.org/jira/browse/HBASE-15464
>             Project: HBase
>          Issue Type: Sub-task
>          Components: metrics
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>
>
> We can add a couple of metrics related to flushes and compactions: 
>  - flush memstore and output file size histogram: This will allow seeing 
> whether we are flushing too early due to memory pressure, too many regions, 
> etc. Tracking flush memstore size vs output file size is useful in 
> understanding the block encoding compression benefits. 
>  - total flushed output bytes: This will allow to monitor the IO / throughput 
> from flushers. You can use this to set num flushers, flush throttle, etc. 
>  - smallCompactionQueueLength / large...: This is tracked, but not emitted 
> anymore due to a bug. 
>  - compaction time histogram: similar to flush time histogram, how long 
> compactions are taking. 
>  - compaction input num files / output num files histogram: How many files on 
> average we are compacting. Stripe compaction / date tiered compaction can use 
> the num output files metric. 
>  - compaction input / output data sizes histogram: How much data on average 
> we are compacting. 
>  - compaction input / output total bytes: Measure compaction IO / throughput. 
> measure write amplification, enables to set compaction throttle. 
>  - Breakdown for above for major compactions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to