I put in a fix a long time ago, so it wouldn't be too hard to redo.
1. Send 500 error until core > 0 numFound.
2. Give it a list of cores.
localhost:8983/solr/ping?check=core1,core2,core3
Then the Amazon load balancer can just check this url with HTTP check
On Thu, Sep 18, 2014 at 3:57 AM, Ere
So, is it possible to configure a ping handler to return quickly with
non-OK status if a search handler is not yet available? This would
allow the load balancer to quickly fail over to another server. I
couldn't find anything like this in the docs, but I'm still hopeful.
I'm aware of the possibil
On 9/17/2014 8:07 PM, Shawn Heisey wrote:
> I've got haproxy in front of my solr servers. My checks happen every
> five seconds, with a 4990 millisecond timeout. My ping handler query
> (defined in solrconfig.xml) is "q=*:*&rows=1" ... so it's very simple
> and fast. Because of efficiencies in t
On 9/17/2014 7:06 AM, Ere Maijala wrote:
> As far as I can see, when a Solr instance is started (whether
> standalone or SolrCloud), a PingRequestHandler will wait until index
> warmup is complete before returning (at least with
> useColdSearcher=false) which may take a while. This poses a problem
As far as I can see, when a Solr instance is started (whether standalone
or SolrCloud), a PingRequestHandler will wait until index warmup is
complete before returning (at least with useColdSearcher=false) which
may take a while. This poses a problem in that a load balancer either
needs to wait
