[
https://issues.apache.org/jira/browse/GEODE-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726180#comment-15726180
]
ASF subversion and git services commented on GEODE-2180:
--------------------------------------------------------
Commit 0bd9fc97acd85cbd4e86d139557b814f1fdf5d55 in geode's branch
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0bd9fc9 ]
GEODE-2180 Autoreconnect with API configuration detail
Autoreconnect assumes valid XML configuration (from the
default use of the cluster config svc). That doesn't
work if the cache is configured using API calls. So,
document this, and suggest disabling either default use
of autoreconnect or default use of the cluster configuration
service.
> Autoreconnect does not work well with configuration via API calls
> -----------------------------------------------------------------
>
> Key: GEODE-2180
> URL: https://issues.apache.org/jira/browse/GEODE-2180
> Project: Geode
> Issue Type: Improvement
> Components: docs
> Reporter: Karen Smoler Miller
> Assignee: Karen Smoler Miller
>
> If autoreconnect is enabled, default reconfiguration upon reconnection uses
> the XML configuration that would be generated by the cluster configuration
> service (also used by default). This set of default settings doesn't work
> when a cache's configuration is accomplished through API calls. So, our
> documentation should explain this, such that admins know when not to enable
> autoreconnect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
