[
https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102933#comment-14102933
]
Erick Erickson commented on SOLR-6392:
--------------------------------------
First, please raise these kinds of issues on the user's list before raising a
JIRA to insure that it's actually a bug.
Configs aren't read to local nodes until the collection is reloaded. This
happens when the Solr instance starts or when the collection is reloaded. So
what you're seeing is what I would expect (or I'm not getting it). I don't
quite remember if 4.4 has the ReloadCollection Collections API call, see:
https://cwiki.apache.org/confluence/display/solr/Collections+API. If it does,
then issuing it after you've uploaded the second set of configs should do the
trick.
If that turns out to be the problem, please close this JIRA as "invalid".
Best,
Erick
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
