: Thanks for the response. I was actually talking about the initial : sync over from the master. what I'd like I guess is a "lock" command : which would start true, and when snapinstaller ran successfully for : the first time would become false. I can write the bash, but I'm not : sure how to get solr to to push out the 503 (I guess that would be the : appropriate code)...
You can configure the "ping" url (admin/ping) to return a 503 unless a specific flag file exists, there's a commented out example of this in the example solrconfig.xml; that's the specific reason the ping URL was created (for Load Blaancers). you could have a simple script that runs snappuller; snapinstaller; sleep XX; touch server-enabled as your way of bringing a new slave online. (Hmm: for some reason, even though PingRequestHandler was written to replace the old ping.jsp, PingRequestHandler still looks for <healthcheck> in the <admin> section instead of it's own init params .. something to make a note of when using it) -Hoss
