[
https://issues.apache.org/jira/browse/HBASE-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark resolved HBASE-4038.
----------------------------------
Resolution: Not a Problem
Metrics now has per region metrics. This should allow anyone to look and see
which region on a server is the hot region.
HTrace has been implemented so we should be able to see what's the hot row in a
region using sampling.
All of the tools suggested in this issue are there. Lets close this an file any
issues dealing with the specific parts separately.
> Hot Region : Write Diagnosis
> ----------------------------
>
> Key: HBASE-4038
> URL: https://issues.apache.org/jira/browse/HBASE-4038
> Project: HBase
> Issue Type: Improvement
> Components: Client, regionserver
> Affects Versions: 0.92.0
> Reporter: Nicolas Spiegelberg
> Assignee: Riley Patterson
> Priority: Minor
>
> We should provide a basic way for end users to operationally diagnose hot row
> problems. Thinking about a 2-phase approach:
> 1. Diagnose hot regions
> 2. Inspect those regions/servers to find the hot rows.
> To diagnose hot regions, we could query the master or regionservers for these
> regions + sort. To inspect the regions for hot rows, we could write another
> script to analyze the HLogs on a server and basically do: sort log|uniq
> -n|sort -n|top
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
