[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035192#comment-15035192 ] Frank Kelly commented on SOLR-6392: --- Was there ever a resolution to this - either a code issue or a user error. I think I am seeing this also (working through the user list right now) > 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.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035222#comment-15035222 ] Erick Erickson commented on SOLR-6392: -- Frank: Here's the rules if you don't specify a configName when issuing the Collections API CREATE command (at least as I understand them) 0> if there are no config sets in ZK, fail 1> if there's a configset with the same name as the collection use it. 2> else if there's only a single configset, use that regardless of whether name matches or not. 3> else if there's more than one configset, fail. The above if (and only if) there is no config specified when creating the collection. If you do specify a configset name, then of course it has to be there or collection creation fails. So here's one possible sequence leading to what's described here: 1> upload a config set with a name of "bonkers". 2> create collection1 with or without specifying the configset name 3> create collection2 with or without specifying the configset name Now, both are registered with ZK as using configset "bonkers" and will stay that way unless and until that association is explicitly changed via linkconfig as Mark recommended. It would be dangerous IMO to change the config set associated with collection2 just because someone uploaded a new configset with the name collection2. So I believe this is working as designed, I'm going to close it. We can reopen or create a new JIRA if necessary. > 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.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108994#comment-14108994 ] Ilya Meleshkov commented on SOLR-6392: -- [~dancollins] 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
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109057#comment-14109057 ] Mark Miller commented on SOLR-6392: --- bq. And if I later deliver configs for second collection and restart Solr/reload cores changes is not applied, that is unexpected behavior Use the zkcli link command after 'delivering' the second set of configs to link them to the collection. 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
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108092#comment-14108092 ] Shawn Heisey commented on SOLR-6392: bq. I don't quite remember if 4.4 has the ReloadCollection Collections API call It does -- in fact, some of the earlier releases had a problem with reloads on cores or collections in cloud mode. See SOLR-4805. 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
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103516#comment-14103516 ] Ilya Meleshkov commented on SOLR-6392: -- Hello, sorry for missing user list step - it my fail. Regarding the issue - I forget to mention that I reloaded both collections without errors after deliver config for second collection. It doesn't seem to have an effect. Please let me know if I could provide some details that could help you investigate the issue. Sunny regards, Ilya 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
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[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
[ https://issues.apache.org/jira/browse/SOLR-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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