You are viewing a single comment's thread from:
RE: Master Slave Replication in Solr
Isn't there a chance that the Master might become the bottleneck in the system? The problem with master-slave replication for me is that it only scales reads. I always try to go Master-Master for the cost of more messages.
I was thinking of doing the same but I will keep Slave too. I was thinking of creating Master-Master using Sharding and then I will also keep Replication with Slave in-place. I don't want my queries to get slower because of indexing documents.
Yeah, when you do sharding indexing can get ugly, that's why I always did full replication until now, disk space is rarely a bottleneck.
I would only go for sharding if I'd have geographical distribution and it makes sense to store the relevant user data closer to the end user.
That's absolutely true...this is where the SolrCloud has an advantage. It does the Replication and Sharing very nicely, just that you need