[
https://issues.apache.org/jira/browse/HBASE-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448231#comment-13448231
]
stack commented on HBASE-3886:
------------------------------
Nah. If restarted, same host and port but the startcode should be different
(irrespective of IP).
> HServerInfo (and ServerName) equate the same if the hostname and port are
> same even if IP has changed
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-3886
> URL: https://issues.apache.org/jira/browse/HBASE-3886
> Project: HBase
> Issue Type: Improvement
> Reporter: stack
>
> This is an interesting one. HServerInfo is deprecated in TRUNK and replaced
> effectively by a new class ServerName. Both equate instances of HSI or SN if
> the two instances have the same hostname and port. Well, thats well and good
> but what if we are getting signals from a server whose IP has changed? In
> this case, we'll see the server in its new location come in but we'll treat
> it as though we'd seen it already, thought its IP had changed. We don't want
> this.
> This facility is needed for rare case where a server is moved from one IP to
> another.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
