I have 3 vm windows, on all of them is installed solr 5.4.0 and 3.4.6 zookeeper; the two services start automatically when the vm start. After reboot vms the solr does not respond correctly, it gives me error500:
HTTP ERROR 500 Problem accessing /solr/. Reason: Server Error ...
SolrException: Error processing the request. CoreContainer is either
not initialized or shutting down.
Checking the logs I have also seen this error:
o.a.s.c.SolrCore null:org.apache.solr.common.SolrException: Error
occurred while loading solr.xml from zookeeper
Trying to stop the zookeeper and solr services on all vm and start again (before start zookeeper on all vm and after solr), sometimes takes solr starts to work properly; other times by solrcloud section of the UI, we notice that the nodes are in the down state (written brown)
I list the procedures that I run to create the cluster solr:
- create folder "zookeeper/data" and changed the zoo.cfg file
by adding the zookeeper nodes in this way
- created the myid files with the respective number on the nodes (1, 2,
3) in the zookeeper\data
- by NSSMs I created zk service that starts the script
zookeeper\bin\zkServer.cmd, and the solr service that starts
solr\bin\solr.cmd with the following parameters
-c -z "zknode1:2181,zknode2:2181,zknode3:2181" -f
I create a collection based on an existing configuration on solr not cloud
solr.cmd create_collection -c mycoll -d C:\conf\mycoll\conf -n mycoll
-shards 1 -replicationFactor 3
on each solr node is see that is created mycoll_shard1_replicaX folder, where X changes on each node (1,2,3). Querying all works, even dataimport, but if I restart the nodes, finding the problem written above. I'm wrong in the creation of the collection, or is this a known bug?