Affects Version/s: None
Fix Version/s: 0.90.0
After split, master attempts to reassign a region to a region server. Occasionally, such a region can get permanently offlined.
Relevant section of META.
Note that these are the only two entries for the problem region. The first one is the parent region (and this problem
region is its splitB). For the next one, note that there is no "info:server" and "info:serverstartcode" columns.
I think Karthik has a handle on the first part (i.e. why the RS ran into the version mismatch, and aborted opening the region). He'll add details to the JIRA. But what we aren't clear about at this stage is why the base scanner didn't kick in and try to reassign the region.
BTW, HBase "hbck" reported this as well (which was good!):
|Field||Original Value||New Value|
|Assignee||Karthik Ranganathan [ karthik.ranga ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||0.90.0 [ 12313607 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1d 2h 25m||1||Jean-Daniel Cryans||23/Jul/10 23:45|