Sorry I misunderstood. I am having difficulty finding this but it's never clear the exact load order. It seems odd that you'd be getting requests when the filter (DispatchFilter) hasn't 100% loaded yet.
I didn't think that the admin handler would allow requests while the dispatch filter is still init'ing but sounds like it is? I'll have to play with this to see.. curious what the problem is for we have a similar setup but not as bad of an init problem (plus when I deploy, my deploy script runs some actual simple test queries to ensure they return before enabling the ping handler to return 200s) to avoid this problem. Cheers Amit On Thu, Nov 8, 2012 at 1:33 PM, Aaron Daubman <daub...@gmail.com> wrote: > 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 > > > > > >
