Erick is right, you have been put in a terrible position.
You need to get agreement, in writing, that it is OK for search to go down when
one server is out of service. This might be for scheduled maintenance or even a
config update. When one server is down, search is down, period.
This requirem
bq: but we have limitation on the number of servers that we can use due to
budget
concerns (limit is 2)
really, really, really push back to your project managers on this. So what
you need 3 machines for a ZooKeeper quorum? The needs of ZK are quite
light, they don't need a powerful machine. Your
Hi Erick,
Thanks a lot for your explanation. We initially considered Solr Cloud but we
have limitation on the number of servers that we can use due to budget
concerns (limit is 2) Solr Cloud requires minimum 3. I have tried out the
solution you suggested and so far its going well and we are not doi
Yes. This is going to hurt you a lot. The intent of M/S is that
you should be indexing to one, and only one machine, the
master. All slaves pull their indexes from the master. Frankly
I don't know quite what will happen in the configuration you're
talking about. I strongly recommend you do not do t
