[
https://issues.apache.org/jira/browse/HBASE-25159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518938#comment-17518938
]
Claire Iacono commented on HBASE-25159:
---------------------------------------
Is this bug getting any traction for an upcoming release? We've had to resolve
this issue a couple times now, following the steps outlined above manually to
fix things. It would be great to have this adoption service as part of hbck2.
Also:
{code:java}
They should have been cleaned up as part of normal processing but for whatever
reason, they were not. {code}
Do we have any idea of what could be the root cause that results in these
orphan regions?
> [hbck2] Add an 'adoption service' for 'Orphaned Regions'
> --------------------------------------------------------
>
> Key: HBASE-25159
> URL: https://issues.apache.org/jira/browse/HBASE-25159
> Project: HBase
> Issue Type: Bug
> Components: hbck2
> Reporter: Michael Stack
> Priority: Major
>
> The 'HBCK Report' has a section for 'Orphaned Regions', regions in the
> filesystem that are no longer referenced by the running hbase. They should
> have been cleaned up as part of normal processing but for whatever reason,
> they were not. Usually these are dessicated directories with nothing in them
> but sometimes they might have an hfile or two. They could have content in
> recovered.edits directory too.
> The "HBCK Report" page outline how to run the bulk load tool. This will pick
> up any hfiles in the 'Orphan Region' if there is worry that they have been
> dropped mistakenly.
> For the content under 'recovered.edits', the WALPlayer has just been adjusted
> so it can pick up this content (See over in HBASE-22976).
> The 'adoption service' would be run over an orphan region and it would apply
> the 'bulk load' if hfiles found and the WALPlayer if 'recovered.edits'
> found... it would then clean up the region directory on successful load after
> leaving audit so the 'orphan' was cleaned-up.
> hbck2 tool would run the adoption service at first. Once we had some
> experience and confidence that the adoption service was running smoothly,
> we'd consider integrating it into the catalogjanitor.
> The 'adoption service' first gets mention in the body of HBASE-21745
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
