You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/18 00:10:00 UTC

[jira] [Commented] (GEODE-6292) Hot loop when joining if locator-wait-time is set and there are no locators

    [ https://issues.apache.org/jira/browse/GEODE-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745649#comment-16745649 ] 

ASF subversion and git services commented on GEODE-6292:
--------------------------------------------------------

Commit fc574dffefad90848b2c2e6f924241596316a0da in geode's branch refs/heads/feature/GEODE-6292 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=fc574df ]

GEODE-6292 hot loop in GMSJoinLeave.findCoordinator

Added a 1 second pause before retrying if no locators could
be contacted and locator-wait-time has been set.


> Hot loop when joining if locator-wait-time is set and there are no locators
> ---------------------------------------------------------------------------
>
>                 Key: GEODE-6292
>                 URL: https://issues.apache.org/jira/browse/GEODE-6292
>             Project: Geode
>          Issue Type: New Feature
>          Components: membership
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Major
>
> If you start up a locator and three servers and then kill two of the servers the locator and remaining server will go into auto-reconnect mode.  When they attempt to start up they will run a hot thread if locator-wait-time is set because there is no stall in the loop that contacts locators for the duration of this wait time in GMSJoinLeave.findCoordinator().



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