"Make the master a slave of the slaves"... Sounds like
an infinite loop to me ...
You don't have to "bring the old master back online". Just
leave the promoted slave as the new master forever and then
create a new slave.
If you have significant differences between hardware for
master and slave, t
Hi Erick,
Thank you for the advice. Given what you've told us, we've modified our plan
to include three physical boxes: one master indexer, and two slaves. I have
a question, however.
Suppose that the master node goes down and we promote the designated slave
to take over. The new master node will
More hardware ...
Here's one scenario...
If you set up a master and two slaves, and then front the slaves
with a load balancer your system will be more robust.
In the event a slave goes down, all search requests will be handled
by the remaining slave while you create a new slave, have it replica
Hello,
Our development team is currently looking into migrating our search system
to Apache Solr, and we would greatly appreciate some advice on setup. We are
indexing approximately two hundred million database rows. We add about a
hundred thousand new rows throughout the day. These new database r
