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 configs
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 ty
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 Ad
Did you upload the modified schema.xml to ZooKeeper? If you had
already (unsuccessfully) attempted to create a collection called
"test2" then you must first delete that collection (using the
collection API) and create it fresh again.
On Thu, Sep 3, 2015 at 12:28 PM, shacky wrote:
> Hi,
> I have a
Hi,
I have a three nodes Solr 5.3.0 cluster with Zookeeper 3.4.5.
New collections are creating without any problem, so the cluster seems
to work well.
I created a new collection "test2" using an old configuration, and I
got this error:
enablePositionIncrements is not a valid option as of Lucene 5.
