John Blum commented on GEODE-1986:
"But if a locator has cluster config running and is secured, any member without
use-cluster-config will be rejected."
Why? This suggests the joining member (server) must enable cluster config in
order to pick up the security configuration so that it "matches" the auth of
the other members (servers) in the cluster. This was never the original
intention of cluster config and suggests you are piggy backing on cluster
config to propagate the security config.
What happens when a Locator is secured but does not have the cluster config
service running? Is that what you mean by this...
"without our current implementation, a server with correct credentials and use
SSL would successfully join a secured locator but itself can be unprotected."
> The Cluster Configuration Service must absolutely not be required to run
> Key: GEODE-1986
> URL: https://issues.apache.org/jira/browse/GEODE-1986
> Project: Geode
> Issue Type: Bug
> Components: configuration
> Reporter: John Blum
> Assignee: Jinmei Liao
> Priority: Critical
> Labels: ClusterConfig, ClusterConfigurationService
> Attachments: App.java
> A bug was introduced in Geode when the logic to fetch the Cluster
> Configuration meta-data from the Locator in the cluster by a joining member
> was refactored into it's own
> causing the following issues...
> 1. First, and foremost, the _Cluster Configuration_ service is now, seemingly
> no longer *optional* (hence, _required_), which is both short sighted and too
> restrictive, and will break existing [embedded Geode application]
> deployments, particularly in situations where GemFire config, and especially,
> _Gfsh_ were not used to configure the cluster, which will be true when users
> upgrade existing clusters based on an earlier versions of Apache Geode
> (namely GemFire < v7.0, once GemFire 9 is based on Apache Geode) and as well
> as _Spring_ applications.
> This change is apparent from the removal of the [conditional check on the
> Geode System property
> which is no longer present [here
> or possibly [here
> 2. This does not work in the embedded Locator case. If a user configures a
> peer Cache using the following in his/her application...
> ... = new CacheFactory()
> .set("name", "Example")
> .set("start-locator", "localhost")
> And another members joins, the logic in (2) above, will fail with...
> Caused by: org.apache.geode.GemFireConfigException: cluster configuration
> service not available
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:181)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:231)
> ... 42 more
> Caused by:
> Unable to retrieve cluster configuration from the locator.
> ... 47 more
This message was sent by Atlassian JIRA