[
https://issues.apache.org/jira/browse/HBASE-21626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742767#comment-16742767
]
stack commented on HBASE-21626:
-------------------------------
Bring it back to branch-2 and branch-2.1 [~sershe]? Its nice operator tool.
On your commit, it's lovely. No need of the ugly hadoop ':' colon-thingy
between JIRA # and summary. No worries on reviewer. Usually it is the
Signed-off-by as you did for the Tommy Li commit recently. And you can add
folks too; i.e. you could have added me for instance since I like this patch so
much (smile) but no harm done. In generally we've been trying to get reviewers
credit via the Signed-off-by: FYI. Especially for non-committers so candidates
can build a track record via the reviewing route (reviewers get double-points
in the eyes of some PMCers -- ha!).
> log the regions blocking WAL from being archived
> ------------------------------------------------
>
> Key: HBASE-21626
> URL: https://issues.apache.org/jira/browse/HBASE-21626
> Project: HBase
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-21626.01.patch, HBASE-21626.02.patch,
> HBASE-21626.patch
>
>
> The WALs not being archived for a long time can result in a long recovery
> later. It's useful to know what regions are blocking the WALs from being
> archived, to be able to debug flush logic and tune configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
