[
https://issues.apache.org/jira/browse/HBASE-20806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527627#comment-16527627
]
Abhishek Singh Chouhan commented on HBASE-20806:
------------------------------------------------
Added a simple patch that adds the journaling functionality (much like the
earlier split one) to monitoredTask, this is disabled by default and enabled
only for flush and compaction(since monitored tasks are also used in other
places such as rpcs etc.). Will add patch for master too.
Looks something like this:
2018-06-28 21:42:00,959 DEBUG [main] regionserver.HRegion(2129): Flush status
journal:
Acquiring readlock on region at 1530202320737
Obtaining lock to block concurrent updates at 1530202320738
Preparing to flush by snapshotting stores in
bd201548dcb5ac5a951e54af54618b97 at 1530202320738
Finished memstore snapshotting
testCompactionFailure,,1530202319214.bd201548dcb5ac5a951e54af54618b97., syncing
WAL and waiting on mvcc, flushsize=2952768 at 1530202320747
Flushing stores of
testCompactionFailure,,1530202319214.bd201548dcb5ac5a951e54af54618b97. at
1530202320749
Flushing colfamily11: creating writer at 1530202320755
Flushing colfamily11: appending metadata at 1530202320908
> Split style journal for flushes and compactions
> -----------------------------------------------
>
> Key: HBASE-20806
> URL: https://issues.apache.org/jira/browse/HBASE-20806
> Project: HBase
> Issue Type: Improvement
> Reporter: Abhishek Singh Chouhan
> Assignee: Abhishek Singh Chouhan
> Priority: Minor
> Attachments: HBASE-20806.branch-1.001.patch
>
>
> In 1.x we have split transaction journal that gives a clear picture of when
> various stages of splits took place. We should have a similar thing for
> flushes and compactions so as to have insights into time spent in various
> stages, which we can use to identify regressions that might creep up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
