Hi, I am hosting Zookeeper ensemble and Solr servers on Microsoft cloud (Azure). From time to time machines are forced to restart to install updates. Recently, this happened again and it caused Zookeeper ensemble and Solr instances to go down. When the machines came back up again. I tried the following
1) Started Zookeeper on all machines using the following command zkServer.cmd (on all three machines) 2) Started Solr on two of those machines using solr.cmd start -c -p 8983 -h [server1_name] -z "[server1_ip]:2181,[server2_name]:2181,[server3_name]:2181" solr.cmd start -c -p 8983 -h [server2_name] -z "[server2_ip]:2181,[server1_name]:2181,[server3_name]:2181" solr.cmd start -c -p 7574 -h [server1_name] -z "[server1_ip]:2181,[server2_name]:2181,[server3_name]:2181" solr.cmd start -c -p 7574 -h [server2_name] -z "[server2_ip]:2181,[server1_name]:2181,[server3_name]:2181" After several trials, it did start Solr on both machines but *non of the previous collections came back normally.* When I look at the admin page, it shows errors as follows *[Collection_name]_shard2_replica2:* org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Index locked for write for core '[Collection_name]_shard2_replica2'. Solr now longer supports forceful unlocking via 'unlockOnStartup'. Please verify locks manually! So probably I am doing something wrong or there is a different way of bringing old collections up. Appreciate your comments/feedback regarding this. Regards, Salman
