[
https://issues.apache.org/jira/browse/HBASE-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-3886.
--------------------------
Resolution: Won't Fix
Resolving. I don't remember why I filed this originally.
If a server comes in w/ a new IP and its 0.96, its ServerName should be
different because it should have a different startcode.
If a server has its IP changed and its still serving the regions it had before
the IP change (and no restart), we shouldn't care the IP changed.
> 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
