Hi Aaron, Check out http://lucene.apache.org/solr/api-4_0_0-BETA/org/apache/solr/handler/PingRequestHandler.html You'll see the ?action=enable/disable. I have our load balancers remove the server out of rotation when the response code != 200 for some number of times in a row which I suspect you are doing too. If I am rolling releasing our search code to production, it gets disabled, sleep for some known number of seconds for the LB to yank the search server out of rotation, push the code, execute some queries using CURL to ensure a response (the warming process should block the request until done) and then enable.
HTH! Amit On Thu, Nov 8, 2012 at 2:01 PM, Aaron Daubman <daub...@gmail.com> wrote: > > (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. > > > > What are you doing to programmatically disable/enable the ping handler? > This sounds like exactly what I should be doing as well... >
