I doubt SOLR-6246 is related, DirectSolrSpellChecker just looks in the index using (on a quick scan) IndexReader which doesn't hold a lock IIUC so it shouldn't leave anything around. Additionally, there is no real "build" step since it's looking at the index rather than creating a new one as AnalyzingInfixSuggester does. The write lock in that JIRA was for the "sidecar" index that AnalyzingInfixSuggester created.
Which doesn't help your original issue. Have you tried specifying the "async" parameter when you issue the RELOAD command then checking the status with REQUESTSTATUS? I'm wondering if you restart your cluster _after_ the reload is successfully completed whether you'd have the same problem. Or whether you'd get some more helpful information if the request actually fails somehow. Also, why issue a reload? If you're re-indexing in the background and want to atomically switch you could use collection aliasing (obviously you'd need more disk space/resources which may make it not a viable option). It looks like > alias points to C1 > create C2 (or delete all data in an existing C2) > index to C2 > check C2 > point alias to C2 Next time of course you index to C1 and switch the alias to C1 when you're happy with it. But even if you do the alias thing it'd still be good to see if we can figure out what's going on because on the surface what you're describing should be OK. Best, Erick On Fri, Jul 14, 2017 at 8:11 AM, alessandro.benedetti <a.benede...@sease.io> wrote: > I have been recently facing an issue with the Collection Reload in a couple > of Solr Cloud clusters : > > 1) re-index a collection > 2) collection happily working > 3) trigger collection reload > 4) reload times out ( silently, no message in any of the Solr node logs) > 5) no effect on the collection ( it still serves query) > > If I restart, the collection doesn't start as it finds the write.lock in the > index. > Sometimes this even avoid the entire cluster to be restarted ( even if the > clusterstate.json actually shows only few collection down) and Solr is not > reachable. > Of course i can mitigate the problem just cleaning up the indexes and > restart (avoiding the reload in favor of just restarts in the future), but > this is annoying. > > I index through the DIH and I use a DirectSolrSpellChecker . > Should I take a look into Zookeeper ? I tried to check the Overseer queues > and some other checks, not sure the best places to look though in there... > > Could this be related ?[1] I don't think so, but I am a bit puzzled... > > [1] https://issues.apache.org/jira/browse/SOLR-6246 > > > > > > > ----- > --------------- > Alessandro Benedetti > Search Consultant, R&D Software Engineer, Director > Sease Ltd. - www.sease.io > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Apache-Solr-4-10-x-Collection-Reload-times-out-tp4346075.html > Sent from the Solr - User mailing list archive at Nabble.com.
