You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (JIRA)" <ji...@apache.org> on 2019/02/04 15:30:00 UTC
[jira] [Created] (HBASE-21843) AM misses region assignment in
catastrophic scenarios where RS assigned to the region in Meta does not
have a WAL dir.
Wellington Chevreuil created HBASE-21843:
--------------------------------------------
Summary: AM misses region assignment in catastrophic scenarios where RS assigned to the region in Meta does not have a WAL dir.
Key: HBASE-21843
URL: https://issues.apache.org/jira/browse/HBASE-21843
Project: HBase
Issue Type: Task
Reporter: Wellington Chevreuil
Assignee: Wellington Chevreuil
A bit unusual, but managed to face this twice lately on both distributed and local standalone mode, on VMs. Somehow, after some VM pause/resume, got into a situation where regions on meta were assigned to a give RS startcode that had no corresponding WAL dir.
That caused those regions to never get assigned, because the given RS startcode is not found anywhere by RegionServerTracker/ServerManager, so no SCP is created to this RS startcode, leaving the region "open" on a dead server forever, in META.
Could get this sorted by adding extra check on loadMeta, checking if the RS assigned to the region in meta is not online and doesn't have a WAL dir, then mark this region as offline.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)