An option is to wrap your Solr slave in a beanstalk and have it take care of
the auto-scaling.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-scaling-solr-setup-tp3029913p3511140.html
Sent from the Solr - User mailing list archive at Nabble.com.
Yes sadly .. I too have not much clue about AWS.
The SolrReplication API doesnt give me what i want exactly.. For the time
being i have hacked my way into the amazon image bootstrapping the
replication check in a shell script ((curl & awk) very dirty way) . Once the
check suceeds I enable the ser
The HTTP interface (http://wiki.apache.org/solr/SolrReplication#HTTP_API)
can be used to control lots of parts of replication.
As to warmups, I don't know of a good way to test that. I don't know whether
getting the current status on the slave includes whether warmup is completed
or not. At worst,
So i am trying to setup an auto-scaling search system of ec2 solr-slaves
which scale up as number of requests increase and vice versa
Here is what I have
1. A solr master and underlying slaves(scalable). And an elastic load
balancer to distribute the load.
2. The ec2-auto-scaling setup fires nodes