[
https://issues.apache.org/jira/browse/GEODE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893081#comment-16893081
]
Darrel Schneider commented on GEODE-6712:
-----------------------------------------
Without this fix if your locator starts but failed to start the cluster config
service then future gfsh commands can just hang forever.
You can confirm if it started by checking the locator log for this info
message: “Cluster configuration service start up completed successfully and is
now running ....”. If you do not see this message then something is wrong.
{{If an exception was thrown from
InternalConfigurationPersistenceService.removeInvalidXmlConfigurations the
cluster config dlock was never released causing future gfsh commands to hang.
As a workaround, if you fix whatever caused the exception and then restart the
locator that logged the exception the dlock should be released and gfsh command
will no longer hang.}}
> Locator should not start if ClusterConfigurationPersistenceService fails to
> start
> ---------------------------------------------------------------------------------
>
> Key: GEODE-6712
> URL: https://issues.apache.org/jira/browse/GEODE-6712
> Project: Geode
> Issue Type: Improvement
> Components: docs, management
> Reporter: Jens Deppe
> Assignee: Jinmei Liao
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In {{InternalLocator.startConfigurationPersistenceService}} we're just
> catching {{Exception}}, logging it and continuing on with locator startup.
> Any exceptions here should fail startup.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
