You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2012/06/01 15:57:23 UTC

[jira] [Commented] (HBASE-6147) SSH and AM.joinCluster leads to region assignment inconsistency in many cases.

    [ https://issues.apache.org/jira/browse/HBASE-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287410#comment-13287410 ] 

ramkrishna.s.vasudevan commented on HBASE-6147:
-----------------------------------------------

We got the following case
-> Initially we had 2 RS and 1 Master with few regions
-> Stopped the cluster and restarted the master and 2 RS.
-> One of the RS znode was not yet deleted but the master started coming up.
-> Here we will now see that there is a server which dead and not yet expired so we wil call expireServer which inturn calls SSH.
-> After this the master sees this as a clean cluster startup.
-> Now SSH triggers one assignment and master startup starts bulk assignment.
-> Now when the znode is present already the Bulk assignment will make the master go down.
So we need to handle such cases.  Solving this should help us to solve most of the double assignment cases.  There can be more such scenarios.
                
> SSH and AM.joinCluster leads to region assignment inconsistency in many cases.
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-6147
>                 URL: https://issues.apache.org/jira/browse/HBASE-6147
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.1, 0.94.0
>            Reporter: ramkrishna.s.vasudevan
>             Fix For: 0.92.2, 0.96.0, 0.94.1
>
>
> We are facing few issues in the master restart and SSH going in parallel.
> Chunhui also suggested that we need to rework on this part.  This JIRA is aimed at solving all such possibilities of region assignment inconsistency

--
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