Thanks Shawn and Elaine, Elaine, Yes all the documents of same route key resides on same shard.
Shawn, I will try to capture the logs. Thanks. Regards, Anil On 25 March 2016 at 02:57, Elaine Cario <etca...@gmail.com> wrote: > Anil, > > I've seen situations where if there was a problem with a specific query, > and every shard responds with the same error, the actual exception gets > hidden by a "No live SolrServers..." exception. We originally saw this > with wildcard queries (when every shard reported a "too many expansions..." > type error, but the exception in the response was "No live SolrServers..." > error. > > You mention that you are using collapse/expand, and that you have shards - > that could possibly cause some issue, as I think collapse and expand only > work correctly if the data for any particular collapse value resides on one > shard. > > On Sat, Mar 19, 2016 at 1:04 PM, Shawn Heisey <apa...@elyograg.org> wrote: > > > On 3/18/2016 9:55 PM, Anil wrote: > > > Thanks for your response. > > > CDH is a Cloudera (third party) distribution. is there any to get the > > > notifications copy of it when cluster state changed ? in logs ? > > > > > > I can assume that the exception is result of no availability of > replicas > > > only. Agree? > > > > Yes, I think that Solr believes there are no replicas for at least one > > shard. As for why it believes that, I cannot say. > > > > If Solr logged every single thing that happened where zookeeper (or even > > just the clusterstate) is involved, you'd be drowning in logs. Much > > more than already happens. The logfile is already very verbose. > > > > Chances are that at least one of your Solr nodes *did* log something > > related to a problem with that collection before you got the error > > you're asking about. > > > > The "No live SolrServers" error is one that people are seeing quite > > frequently. There may be some instances where Solr isn't behaving > > correctly, but I think when this happens, it usually indicates there's a > > real problem of some kind. > > > > To troubleshoot, we'll need to see any errors or warnings you find in > > your Solr logfiles from the time before you get an error on a request. > > You'll need to check the logfile on all Solr nodes. > > > > It might be a good idea to also involve Cloudera support, see what they > > think. > > > > Thanks, > > Shawn > > > > >
