[
https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108994#comment-14108994
]
Ilya Meleshkov edited comment on SOLR-6392 at 8/25/14 10:58 AM:
----------------------------------------------------------------
[~dancollins] you wrote:
{quote}
You have 2 collections which should be using independent configurations (both
stored in ZK).
{quote}
correct
{quote}
If you change config1 (and restart Solr), that takes effect (in collection1 or
both?)
{quote}
That takes an effect for both collections. I'm checking using
http://solrhost/solr/#/collectionName/schema
{quote}
If you change config2 (and restart Solr), there is no apparent effect?
{quote}
Neither restart of Solr or reloading cores makes a difference. Second config is
not applied.
{quote}
First question is then, are you sure both collections are using different
configs, or have they somehow both picked up the same config?
{quote}
Since if I deliver configs for both collections and then start Solr it works
fine, I make an assumptions that configurations are correct and collections use
specific configs
{quote}
How did you set them up, and how did you define which config each collection
uses?
{quote}
Configs delivered to ZK using following command
{code:none}
java -cp org.apache.solr.cloud.ZkCLI -cmd upconfig -zkhost ${zk.urls} -confdir
%CONFIG_PATH% -confname ${solr.collection.name}
{code}
The {{solr.solr.home}} is configured manually and contains {{cores}} folder
with subfolder for each collection. Subfolder names match collections names.
Each collection subfolder has {{core.properties}} with following text:
{code:none}
name=collectionName
{code}
{quote}
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.
{quote}
Ok, it looks to be very close to problem I have, but I explicitly specify
collection names for both collections. And if I deliver configs for both
collections and restart Solr/reload cores changes is not applied, that is
unexpected behavior
was (Author: imeleshkov):
[~dancollins] you wrote:
{quote}
You have 2 collections which should be using independent configurations (both
stored in ZK).
{quote}
correct
{quote}
If you change config1 (and restart Solr), that takes effect (in collection1 or
both?)
{quote}
That takes an effect for both collections. I'm checking using
http://solrhost/solr/#/collectionName/schema
{quote}
If you change config2 (and restart Solr), there is no apparent effect?
{quote}
Neither restart of Solr or reloading cores makes a difference. Second config is
not applied.
{quote}
First question is then, are you sure both collections are using different
configs, or have they somehow both picked up the same config?
{quote}
Since if I deliver configs for both collections and then start Solr it works
fine, I make an assumptions that configurations are correct and collections use
specific configs
{quote}
How did you set them up, and how did you define which config each collection
uses?
{quote}
Configs delivered to ZK using following command
{code:none}
java -cp org.apache.solr.cloud.ZkCLI -cmd upconfig -zkhost ${zk.urls} -confdir
%CONFIG_PATH% -confname ${solr.collection.name}
{code}
The {{solr.solr.home}} is configured manually and contains {{cores}} folder
with subfolder for each collection. Subfolder names match collections names.
Each collection subfolder has {{core.properties}} with following text:
{code:none}
name=collectionName
{code}
> 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: [email protected]
For additional commands, e-mail: [email protected]
