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

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

Commit 197555616a479a5dde5c8939bdb52efd751cc901 in incubator-geode's branch 
refs/heads/feature/GEODE-831 from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1975556 ]

GEODE-965: redundant cache server created during auto-reconnect

If cluster configuration is enabled but a cache.xml is actually being
used to construct the cache then it is possible that after an auto-
reconnect a redundant CacheServer will be created.

There is an assumption made in writing the auto-reconnect code that if
cluster-configuration is enabled the cache will not be constructed
using a cache.xml file.

This change-set marks CacheServers that are created by gfsh or so
called "default" servers created by cache.xml processing so that
auto-reconnect will know whether they should be handled specially.


> On auto-reconnect a redundant CacheServer is created if one is specified in 
> cache.xml and cluster-config is enabled
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-965
>                 URL: https://issues.apache.org/jira/browse/GEODE-965
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server, membership
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>             Fix For: 1.0.0-incubating.M2
>
>
> If cluster configuration is enabled but a cache.xml is actually being used to 
> construct the cache then it is possible that after an auto-reconnect a 
> redundant CacheServer will be created.
> There is an assumption made in writing the auto-reconnect code that if 
> cluster-configuration is enabled the cache will not be constructed using a 
> cache.xml file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to