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 2019/02/12 16:16:00 UTC

[jira] [Assigned] (GEODE-6393) Remove synchronization lock in favor of AtomicReference for InternalLocator

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

Jens Deppe reassigned GEODE-6393:
---------------------------------

    Assignee: Jens Deppe

> Remove synchronization lock in favor of AtomicReference for InternalLocator
> ---------------------------------------------------------------------------
>
>                 Key: GEODE-6393
>                 URL: https://issues.apache.org/jira/browse/GEODE-6393
>             Project: Geode
>          Issue Type: Improvement
>          Components: locator
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>
> Although we explicitly state that multiple locators should be started serially, a network outage (and recovery) may result in multiple locators entering a reconnect state simultaneously. In this situation a deadlock may result. This is particularly likely when cluster config is enabled (because of region creation).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)