[
https://issues.apache.org/jira/browse/SOLR-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948866#comment-13948866
]
Shalin Shekhar Mangar edited comment on SOLR-5919 at 3/27/14 5:05 AM:
----------------------------------------------------------------------
I think that is completely fine and as per design. The control server is also
aware of Zookeeper and belongs to a collection called control_collection. There
should be one overseer across the entire cluster and it can be any node -having
a shard for any collection- as long as it is aware of the same Zookeeper
ensemble.
was (Author: shalinmangar):
I think that is completely fine and as per design. The control server is also
aware of Zookeeper and belongs to a collection called control_collection. There
should be one overseer across the entire cluster and it can be any node having
a shard for any collection as long as it is aware of the same Zookeeper
ensemble.
> 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.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
