We are using solr 4.3.0 for our search application. We will be splitting shard at run time. I simulated a scenario, let me explain that first.
I am indexing some 20000 docs via solrj. At the same time i m triggering my split shard command. And also, I am killing the leader node when both the above operations are in progress. In the above case i m facing *downtime(indexing fails), document loss,* and also delete shard after split shard not gets completed. <nabble_img src="Solr1.png" border="0" <nabble_img src="Solr3.png" border="0" alt="When i search *:*, i m getting numFound as 0. Doc loss"/>alt="Cloud View after split shard gets completed."/> <http://lucene.472066.n3.nabble.com/file/n4082002/Solr2.png> <http://lucene.472066.n3.nabble.com/file/n4082002/Solr3.png> <http://lucene.472066.n3.nabble.com/file/n4082002/Solr4.png> And also error was thrown during indexing. let me post that too /Doc:::11203 Doc:::11204 1 Aug, 2013 9:24:52 PM org.apache.solr.common.cloud.ZkStateReader$2 process INFO: A cluster state change: WatchedEvent state:SyncConnected type:NodeDataChanged path:/clusterstate.json, has occurred - updating... (live nodes size: 3) Doc:::11205 org.apache.solr.client.solrj.SolrServerException: No live SolrServers available to handle this request at org.apache.solr.client.solrj.impl.LBHttpSolrServer.request(LBHttpSolrServer.java:331) at org.apache.solr.client.solrj.impl.CloudSolrServer.request(CloudSolrServer.java:306) at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117) at org.apache.solr.client.solrj.SolrServer.commit(SolrServer.java:168) at org.apache.solr.client.solrj.SolrServer.commit(SolrServer.java:146) at tokyosolrindex.Main.main(Main.java:44)/ Is there any approach to overcome this??? Thanks in advance RANJITH VENKATESAN -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Split-Shard-Document-loss-and-down-time-tp4082002.html Sent from the Solr - User mailing list archive at Nabble.com.
