You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/03/06 18:32:00 UTC

[jira] [Resolved] (GEODE-4730) Remove DLock acquisition timeouts in ClusterConfigurationService.createConfigurationResponse

     [ https://issues.apache.org/jira/browse/GEODE-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barbara Pruijn resolved GEODE-4730.
-----------------------------------
    Resolution: Fixed

> 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
>            Assignee: Jens Deppe
>            Priority: Major
>             Fix For: 1.6.0
>
>
> 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)