hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12424) Finer grained logging and metrics for split transactions
Date Fri, 07 Nov 2014 01:46:35 GMT

     [ https://issues.apache.org/jira/browse/HBASE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell updated HBASE-12424:
-----------------------------------
    Attachment: HBASE-12424.patch

Updated patch for master. What I plan to commit. Only change is in RSRpcServices I found a
couple of flushcache() calls (for split and merge admin actions) that were not being timed.

> Finer grained logging and metrics for split transactions
> --------------------------------------------------------
>
>                 Key: HBASE-12424
>                 URL: https://issues.apache.org/jira/browse/HBASE-12424
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 0.98.8, 0.99.2
>
>         Attachments: 0001-HBASE-12424-Finer-grained-logging-and-metrics-for-sp.patch,
0002-HBASE-12424-Finer-grained-logging-and-metrics-for-sp.patch, 0003-HBASE-12424-Finer-grained-logging-and-metrics-for-sp.patch,
HBASE-12424-0.98.patch, HBASE-12424.patch, HBASE-12424.patch, HBASE-12424.patch, HowHBaseRegionSplitsareImplemented.pdf
>
>
> A split transaction is a complex orchestration of activity between the RegionServer,
Master, ZooKeeper, and HDFS NameNode. We have some visibility into the time taken by various
phases of the split transaction in the logs. We will see "Starting split of region $PARENT"
before the transaction begins, before the parent is offlined. Later we will see "Opening $DAUGHTER"
as one of the last steps in the transaction, this is after the parent has been flushed, offlined,
and closed. Finally ""Region split, hbase:meta updated, and report to master ... Split took
$TIME" after all steps are complete and including the total running time of the transaction.

> For debugging the cause(s) of long running split transactions it would be useful to know
the distribution of time spent in all of the phases of the split transaction. 



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

Mime
View raw message