[ https://issues.apache.org/jira/browse/HBASE-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056662#comment-13056662 ]
Todd Lipcon commented on HBASE-4038: ------------------------------------ Analyzing the HLogs only gets you hot write, not hot read, right? An RPC sampling approach would be nice. For example, a boolean which can be flipped at runtime to enable reservoir sampling of RPCs, and a servlet which can dump a representative set from the last few minutes. > Hot Region 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: Nicolas Spiegelberg > 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 is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira