You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2018/02/22 22:35:00 UTC
[jira] [Created] (GEODE-4730) Remove DLock acquisition timeouts in
ClusterConfigurationService.createConfigurationResponse
Jens Deppe created GEODE-4730:
---------------------------------
Summary: Remove DLock acquisition timeouts in ClusterConfigurationService.createConfigurationResponse
Key: GEODE-4730
URL: https://issues.apache.org/jira/browse/GEODE-4730
Project: Geode
Issue Type: Improvement
Components: configuration
Reporter: Jens Deppe
Reviewing some of this code with [~upthewaterspout] it seems like it would be worse if the lock acquisition fails and an empty response is returned vs. a hang/deadlock happening on server startup.
At least if there's a hang we'd know it as opposed to a server starting up without any configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)