[
https://issues.apache.org/jira/browse/GEODE-8739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236457#comment-17236457
]
Jason Huynh commented on GEODE-8739:
------------------------------------
yes, these processes happen to have run in Kubernetes. We still think it can
occur with processes not being run in kubernetes but will prove it out in a
test and update the ticket accordingly.
So if we happen to have the same scenario on bare metal, we expect this to not
split? or are we saying that we expect the admin to delete the .dat file before
starting up?
> Split brain when locators exhaust join attempts on non existant servers
> -----------------------------------------------------------------------
>
> Key: GEODE-8739
> URL: https://issues.apache.org/jira/browse/GEODE-8739
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Jason Huynh
> Priority: Major
> Attachments: exportedLogs_locator-0.zip, exportedLogs_locator-1.zip
>
>
> The hypothesis: "if there is a locator view .dat file with several
> non-existent servers then then locators will waste all of their join attempts
> on the servers instead of finding each other"
> Scenario is a test/user attempts to recreate a cluster with existing .dat and
> persistent files. The locators are spun in parallel and from the analysis,
> it looks like they are able to communicate with each other, but then end up
> forming their own ds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
