[jira] Commented: (HBASE-1157) If we do not take start code as a part of region server recovery, we could inadvertantly try to reassign regions assigned to a restarted server with a different start code

["Jim Kellerman (JIRA)" <ji...@apache.org>]

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

Jim Kellerman commented on HBASE-1157:
--------------------------------------

As 0.19.x does not allow a server with the same ip:port number to join the cluster until the previous instance has been recovered, this is not an issue for 0.19.x. However, if we intend to allow a new instance of the same server to start serving regions, we need to be able to differentiate between the dead instance and the new one.

This is my primary reason for making the startcode a part of the regionserver identification.

While we might use a different mechanism after ZK integration, the ZK integration still needs to account for what instance
of the regionserver it is dealing with.


> If we do not take start code as a part of region server recovery, we could inadvertantly try to reassign regions assigned to a restarted server with a different start code
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1157
>                 URL: https://issues.apache.org/jira/browse/HBASE-1157
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master, regionserver
>    Affects Versions: 0.20.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.20.0
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.