You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2018/01/02 20:26:00 UTC
[jira] [Created] (GEODE-4179) Setting ENABLE_CLUSTER_CONFIGURATION
true on non-dedicated-locator fails silently
Kirk Lund created GEODE-4179:
--------------------------------
Summary: Setting ENABLE_CLUSTER_CONFIGURATION true on non-dedicated-locator fails silently
Key: GEODE-4179
URL: https://issues.apache.org/jira/browse/GEODE-4179
Project: Geode
Issue Type: Bug
Components: configuration
Reporter: Kirk Lund
We have some tests that we thought were exercising cluster configuration in a server JVM, but it turns out that setting ENABLE_CLUSTER_CONFIGURATION to true in a Server JVM or application JVM is ignored. It's ignored even in a JVM with a colocated Locator.
Setting this config option in a non-locator should result in a failure to startup with a message that explains that ENABLE_CLUSTER_CONFIGURATION can only be used in a dedicated locator JVM.
I also recommend that we loosen this restriction for a loner so that we can exercise cluster configuration in an IntegrationTest that creates a longer member with ENABLE_CLUSTER_CONFIGURATION. Otherwise, you cannot exercise cluster configuration options in IntegrationTests and you'd have to resort to testing in DUnit with a full cluster that includes a dedicated Locator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)