[
https://issues.apache.org/jira/browse/SOLR-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192692#comment-14192692
]
Mark Miller commented on SOLR-5919:
-----------------------------------
I don't know - depends on how whoever is solving this wants to tackle it.
You could look at starting control after the jetties - then it would end up
last in line (these are horribly started sequentially after all) and
chaosmonkey tests would get a bit more coverage.
You could use the new stuff that lets you prefer nodes as the overseer. That
would increase coverage a bit. Randomly prefer all the collection1 jetties.
Or you could change things at a deeper level to create more separation.
Probably that's ideal, but given I can't work on it soon, I'm just as +1 on
simply getting some Overseer kills in a chaosmonkey run with whatever
improvement.
> 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]
