Configuration upload to zookeeper and collection creation are two separate 
things, although they can be accompished at the same time using /bin/solr.  You 
can upload configurations before you create collections and you can have 
mutiple configurations uploaded to zookeeper at the same time.  I typically 
upload my configurations using zkcli.sh in the server/scripts/cloud-scripts 
directory in Solr and then use curl to send a request to create the collection 
based on a configuration I uploaded to Zookeeper instead of using the /bin/solr 
script to do the upload and creation all at once.  So you may have several 
configs uploaded, but you may not necessarily have created collections for 
them.  

If you need to update the configuration, just re-upload using zkcli.sh (from 
Solr server/scripts/cloud-scripts not ZkCli.sh in zookeeper/bin) and then try 
the collection creation again using curl or the browser to issue the 
Collections API create command.  Re-uploading will overwrite the config in 
Zookeeper.

I don't believe what you are seeing is a bug, as you can upload anything you 
want to Zookeeper, but it doesn't mean it's valid.  Only Solr knows that once 
it tries to load what you've uploaded to Zookeeper.

- Kevin

> On Sep 3, 2015, at 12:36 AM, shacky <shack...@gmail.com> wrote:
> 
> Hi Shalin,
> thank you very much for your answer.
> 
> I found out and managed in recreating the problem.
> 
> I created a new collection, with the wrong configset. I got the error
> and the collection was not created, good.
> But after that I continue to see the "SolrCore Initialization
> Failures" in the Solr Admin web interface on all three nodes.
> I had to restart Solr to remove that error.
> 
> From this point if I try to change the configset and recreate the same
> collection I still continue to get the same previous error.
> 
> So I discovered that the configuration is still in Zookeeper:
> 
> root@index1:~# /usr/share/zookeeper/bin/zkCli.sh
> Connecting to localhost:2181
> Welcome to ZooKeeper!
> JLine support is enabled
> 
> WATCHER::
> 
> WatchedEvent state:SyncConnected type:None path:null
> [zk: localhost:2181(CONNECTED) 0] ls /solr/configs
> [test, test2]
> 
> Even if the "test2" collection was not created due to the previous error.
> 
> I had to remove (rmr) the configuration in Zookeeper to be able to
> recreate the collection.
> 
> I think this is a bug, isn't it?
> The configuration should be removed from Zookeeper if the collection
> was not created due to an error...

Reply via email to