[
https://issues.apache.org/jira/browse/SOLR-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192629#comment-14192629
]
Hoss Man commented on SOLR-5919:
--------------------------------
1 + 2 seem like a chicken and egg to me ... if we leave the control collection
in the cloud (instead of making it it's own isolated solr instance running in
legacy non-cloud mode) then how do you prevent it from participating in
overseer election? we can't allow ChaosMonkey to shutdown the control
collection or comparisons with the control collection won't be reliable, but if
it's always up it will get elected overseer pretty quick, and then overseer is
never at risk anymore.
> AbstractFullDistribZkTestBase: control server thinks it's part of the cloud,
> takes overseer role
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-5919
> URL: https://issues.apache.org/jira/browse/SOLR-5919
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
>
> I was banging my head trying to figure out why SOLR-5795 combined with
> SOLR-5823 wasn't working when I noticed something interesting as a result of
> some gratuituous logging:
> * the control server thinks it's in running in cloud mode, in a cluster
> consisting solely of itself, and acts as overseer
> * none of the nodes in the actual cluster being tested think they are the
> overseer
> ...i haven't dug in very deep, but i suspect that some combination of the
> control server starting up first and thinking it's part of zk is leading to
> it becoming the overseer, even thought it evidently never thinks it's one of
> the leaders/replicas of the cloud cluster.
> It's hard to see this problem w/o SOLR-5823 -- i'll update the patch there
> with a test showing hte problem, but i wanted to make sure it got tracked in
> it's own bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
