Hi All, I am trying to run two SolrCloud with 3 and 2 shards respectively (lets say Cloud3shards and Clouds2Shards). All servers are identical with 18GB Ram (16GB assigned for Java).
I am facing a few issues on both clouds and would be grateful if any one else has seen / solved these. 1) Every now and then, Solr would take off one of the servers (It either shows as "recovering" (orange) or its taken offline completely). The Logging tab on Admin page shows these errors for Cloud3shards /Error while trying to recover:org.apache.solr.client.solrj.SolrServerException: Timeout occured while waiting response from server at: http://xxx:8983/solr/xxx / /Error while trying to recover. core=xxx:org.apache.solr.common.SolrException: I was asked to wait on state recovering for xxx:8983_solr but I still do not see the request state. I see state: recovering live:false/ On the Cloud2shards also I see similar messages I have noticed it does happen more while indexing documents, but I have also seen this happening while only querying Solr. Both SolrClouds are managed by the same Zookeeper ensemble (set of 3 ZK servers). 2) I am able to Commit but Optimize never seems to work. Right now I have an average of 30 segments on every Solr Server. Has any one else faced this issue? I have tried Optimize from the admin page and as a Http post request. Both of them fail. Its not because of the hard disk space since my index size is less than 50Gb and I have 500GB space on each server. 3) If I try to query solr with rows = 5000 or more (for Cloud2) . for cloud1 its around 20,000 documents. org.apache.solr.client.solrj.SolrServerException: No live SolrServers available to handle this request:[http://ABC1:8983/solr/aaa, http://ABC2:8983/solr/aaa]. 4) I have also noticed that ZK would switch leaders every now and then. I am attributing it to point 1 above, where as soon as the leader is down, another server takes its place. My concern is the frequency with which this switch happens. I guess this is completely related to point 1 , and if that is solved, I will not be having this issue either. --Shreejay -- View this message in context: http://lucene.472066.n3.nabble.com/Solr4-0-SolrCloud-queries-tp4016825.html Sent from the Solr - User mailing list archive at Nabble.com.
