On 7/28/2015 8:22 AM, sangeetha.subraman...@gtnexus.com wrote: > org.apache.solr.client.solrj.SolrServerException: > org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error > from server at http://10.111.65.150:8080/solr/umbcollection: No active slice > servicing hash code 103646ce in DocCollection(umbcollection)={ > > "shards":{"shard1":{ > "range":"80000000-ffffffff",
That JSON structure looks like it is a complete collection clusterstate. Which means that you only have one shard, but it is configured to only cover half of the range of hash values. You have nothing covering 00000000 through 7fffffff. That is consistent with the error message. There should be another shard which would cover the other half of the range. It seems highly unlikely that you could have ended up with this clusterstate unless you have been manually changing your collection with the collections API after creating it, or maybe doing manual tweaks to the config in zookeeper. Has anything like that happened? What is your Solr version? Thanks, Shawn