Hi Li, Do you see timeouts liek "CLUSTERSTATUS the collection time out:180s" if its the case, this may be related to https://issues.apache.org/jira/browse/SOLR-7940, and i would say either use the patch file or upgrade.
*Thanks,* *Rajesh,* *8328789519,* *If I don't answer your call please leave a voicemail with your contact info, * *will return your call ASAP.* On Thu, Apr 21, 2016 at 6:02 AM, YouPeng Yang <yypvsxf19870...@gmail.com> wrote: > Hi > We have used Solr4.6 for 2 years,If you post more logs ,maybe we can > fixed it. > > 2016-04-21 6:50 GMT+08:00 Li Ding <li.d...@bloomreach.com>: > > > Hi All, > > > > We are using SolrCloud 4.6.1. We have observed following behaviors > > recently. A Solr node in a Solrcloud cluster is up but some of the cores > > on the nodes are marked as down in Zookeeper. If the cores are parts of > a > > multi-sharded collection with one replica, the queries to that > collection > > will fail. However, when this happened, if we issue queries to the core > > directly, it returns 200 and correct info. But once Solr got into the > > state, the core will be marked down forever unless we do a restart on > Solr. > > > > Has anyone seen this behavior before? Is there any to get out of the > state > > on its own? > > > > Thanks, > > > > Li > > >
