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

ASF subversion and git services commented on GEODE-2804:
--------------------------------------------------------

Commit 92f270805a83c69da2c1ab469b3206ae6e7c9acf in geode's branch 
refs/heads/feature/GEODE-1279 from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=92f2708 ]

GEODE-2804 Caching the InetAddress for configured ip string

1. We keep configure host string in HostAddress class
2. We reuse InetsocketAddress if it is ipString.
3. Client has logic to retry thus we keep InetsocketAddress even if
   it is not ip string.

GEODE-3017 IPv6 issue on windows. Above changes fixed this issue.

GEODE-2940 Now we don't validate configure host string on start. As
there is possibility that host may not available.

1. Earlier wan config were failing because of that. Now we just keep
   those configure host string. And try this later.

Added unit tests for it.


> Allow a locator host to be taken off line and replaced with a different 
> machine having the same host name
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-2804
>                 URL: https://issues.apache.org/jira/browse/GEODE-2804
>             Project: Geode
>          Issue Type: Improvement
>          Components: client/server, membership, native client
>    Affects Versions: 1.1.1
>            Reporter: Bruce Schuchardt
>            Assignee: Hitesh Khamesra
>             Fix For: 1.3.0
>
>
> It is not unlikely that in a long-running system a machine hosting a locator 
> will break down and need to be replace, or that a virtual machine hosting a 
> locator will be stopped and restarted.  In either case the machine may have a 
> different IP address.
> Clients and servers currently cache the IP address of a locator and should be 
> changed to re-resolve the host name if the address stops being usable.
> Servers currently cannot be started if they are given a host name that can 
> not be resolved.  They should be changed to allow this and start up if they 
> are able to contact one or more of the other locators in their "locators" 
> setting.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to