lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6392) If run Solr having two collections configured but only one config delivered to Zookeeper causes that config is applied for all collections
Date Wed, 20 Aug 2014 08:20:26 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103598#comment-14103598
] 

Daniel Collins commented on SOLR-6392:
--------------------------------------

By "deliver config", I am assuming you mean upload that config to zk? Do you use the zkcli.sh
script for that or do you do it via some other means?

What I think you are saying is:

# You have 2 collections which should be using independent configurations (both stored in
ZK).
# If you change config1 (and restart Solr), that takes effect (in collection1 or both?)
# If you change config2 (and restart Solr), there is no apparent effect?

First question is then, are you sure both collections are using different configs, or have
they somehow both picked up the same config?  How did you set them up, and how did you define
which config each collection uses?
There used to be a "fall-back" approach in Solr, if you started a core but didn't tell it
to use any config from ZK AND there was only 1 possible config in ZK, the Solr "guessed" that
was what you meant and set up the links.

I would guess that might what's happened here, so both your collections are actually using
config1.

Check in ZK, under the /collections/<collectionName> node there should be an element
called configName which maps to the configuration in ZK.
If that is wrong, you need to correct that, which is the "-linkconfig" option in zkcli.sh

But as Erick says, this would be better discussed on the list.

> If run Solr having two collections configured but only one config delivered to Zookeeper
causes that config is applied for all collections
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-6392
>                 URL: https://issues.apache.org/jira/browse/SOLR-6392
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.4
>            Reporter: Ilya Meleshkov
>
> I have simplest Solr cloud configured locally. Thus I have single Solr and Zookeeper
nodes. 
> Steps to reproduce an error:
> # have stopped Solr+ZK with two collections
> # run ZK
> # deliver config to one collection only
> # run Solr - Solr running without any complains or errors
> # deliver config to second collection - doesn't have an effect
> But if I deliver configs for both collections before start Solr - it work perfectly.
> So I would say that Solr should fail with meaningful error if there is no config for
some collection.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message