geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Schuchardt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-3094) LocatorUDPSecurityDUnitTest failures
Date Fri, 16 Jun 2017 17:45:02 GMT

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

Bruce Schuchardt updated GEODE-3094:
------------------------------------
    Affects Version/s: 1.1.0

> LocatorUDPSecurityDUnitTest failures
> ------------------------------------
>
>                 Key: GEODE-3094
>                 URL: https://issues.apache.org/jira/browse/GEODE-3094
>             Project: Geode
>          Issue Type: Bug
>          Components: membership
>    Affects Versions: 1.1.0
>            Reporter: Bruce Schuchardt
>
> a new test, testMultipleLocatorsRestartingWithMissingServers, fails off and on when discovery
uses GMSJoinLeave.findCoordinatorFromView() to locate the coordinator.  This appears to be
due to the "registrants" set having members whose PK isn't known.  I'm attaching debug-level
logs of a failed run.
> This relates to GEODE-3052.  Restart of locators isn't a problem if there are servers
still up - it's only when the persistent view is used during locator startup and the view
contains defunct servers, making the locator resort to using findCoordinatorFromView().



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message