Amit, I am using warming /firstSearcher queries to ensure this happens before any external queries are received, however, unless I am misinterpreting the logs, solr starts responding to admin/ping requests before firstSearcher completes, and, the LB then puts the solr instance back in the pool, and it starts accepting connections...
On Thu, Nov 8, 2012 at 4:24 PM, Amit Nithian <anith...@gmail.com> wrote: > I think Solr does this by default and are you executing warming queries in > the firstSearcher so that these actions are done before Solr is ready to > accept real queries? > > > On Thu, Nov 8, 2012 at 11:54 AM, Aaron Daubman <daub...@gmail.com> wrote: > > > Greetings, > > > > I have several custom QueryComponents that have high one-time startup > costs > > (hashing things in the index, caching things from a RDBMS, etc...) > > > > Is there a way to prevent solr from accepting connections before all > > QueryComponents are "ready"? > > > > Especially, since many of our instance are load-balanced (and > > added-in/removed automatically based on admin/ping responses) preventing > > ping from answering prior to all custom QueryComponents being ready would > > be ideal... > > > > Thanks, > > Aaron > > >
