[
https://issues.apache.org/jira/browse/HBASE-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-5094:
------------------------------------------
Description:
R1 is reassigned to RS3 during RS1 shutdown, even though R1 was just assigned
to RS2 by load balancer. So .META. table indicated R1 is on RS3. Both RS2 and
RS3 think they have R1. Later when RS3 shutdown, R1 is reassigned to RS2. RS2
will indicate ALREADY_OPENED. Thus the region is considered assigned to RS2
even though .META. indicates it is on RS3.
1) Region R1 - Assigned from RS1 to RS2.
2) RS1 goes down and ServerShutDownHandler. ServerShutDwonHandler finds R1
with RS1 from META as still META is not yet updated to RS2.
3) As RS1 goes down R1 is assigned from RS1 to RS3.
4) RS3 goes down. ServerShutdownHandler processes R1 and tries to assign it to
RS2.
5) RS2 says ALREADY_OPENED but META shows RS3.
I was able to reproduce the scenario in 0.92
was:
R1 is reassigned to RS3 during RS1 shutdown, even though R1 was just assigned
to RS2 by load balancer. So .META. table indicated R1 is on RS3. Both RS2 and
RS3 think they have R1. Later when RS3 shutdown, R1 is reassigned to RS2. RS2
will indicate ALREADY_OPENED. Thus the region is considered assigned to RS2
even though .META. indicates it is on RS3.
1) Region R1 - Assigned from RS1 to RS2.
2) RS1 goes down and ServerShutDownHandler. ServerShutDwonHandler finds RS1
with R1 from META as still META is not yet updated to RS2.
3) As RS1 goes down R1 is assigned from RS1 to RS3.
4) RS3 goes down. ServerShutdownHandler processes R1 and tries to assign it to
RS2.
5) RS2 says ALREADY_OPENED but META shows RS3.
I was able to reproduce the scenario.
> The META can hold an entry for a region with a different server name from the
> one actually in the AssignmentManager thus making the region inaccessible.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5094
> URL: https://issues.apache.org/jira/browse/HBASE-5094
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
>
> R1 is reassigned to RS3 during RS1 shutdown, even though R1 was just assigned
> to RS2 by load balancer. So .META. table indicated R1 is on RS3. Both RS2 and
> RS3 think they have R1. Later when RS3 shutdown, R1 is reassigned to RS2. RS2
> will indicate ALREADY_OPENED. Thus the region is considered assigned to RS2
> even though .META. indicates it is on RS3.
> 1) Region R1 - Assigned from RS1 to RS2.
> 2) RS1 goes down and ServerShutDownHandler. ServerShutDwonHandler finds R1
> with RS1 from META as still META is not yet updated to RS2.
> 3) As RS1 goes down R1 is assigned from RS1 to RS3.
> 4) RS3 goes down. ServerShutdownHandler processes R1 and tries to assign it
> to RS2.
> 5) RS2 says ALREADY_OPENED but META shows RS3.
> I was able to reproduce the scenario in 0.92
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
