bq: The configuration should be removed from Zookeeper if the collection was not created due to an error...
Well, how about an enhancement? It is a bit confusing that if the configset already exists in ZK, then the second attempt to create a collection with the same configset fails because configsets aren't overwritten if they already exist. See: https://issues.apache.org/jira/browse/SOLR-8008 for several options and feel free to comment on what would be most intuitive. The issue is we don't want to overwrite configsets that other collections may be relying on without some kind of really explicit instruction, but the create case is kind of special in this regard. Best, Erick On Thu, 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...
