[
https://issues.apache.org/jira/browse/HBASE-23322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack updated HBASE-23322:
----------------------------------
Fix Version/s: 2.2.3
2.3.0
3.0.0
Hadoop Flags: Reviewed
Release Note: An hbck2 scheduleRecoveries will run a subclass of
ServerCrashProcedure which asks Master what Regions were on the dead Server but
it will also do a hbase:meta table scan to see if any vestiges of the old
Server remain (for the case where an SCP failed mid-point leaving references in
place or where Master and hbase:meta deviated in accounting).
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged manually to branch-2.2+. Thanks for review [~binlijin]
> [hbck2] Simplification on HBCKSCP scheduling
> --------------------------------------------
>
> Key: HBASE-23322
> URL: https://issues.apache.org/jira/browse/HBASE-23322
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.2.3
>
> Attachments:
> 0001-HBASE-23322-hbck2-Simplification-on-HBCKSCP-scheduli.patch
>
>
> I can make the scheduling of HBCKSCP simpler. I can also fix a bug in parent
> issue that I notice after exercising it a bunch on a cluster.
> The bug is that 'Unknown Servers' seem to be retained in the Map of reporting
> servers. They are usually cleared just before an SCP is scheduled but
> scheduling HBCKSCP doesn't go the usual route.
> The patch here forces HBCKSCP via the usual SCP route only at the scheduling
> time, context dictates whether SCP or the scouring HBCKSCP.
> Let me put up a patch and will test in meantime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
