I cannot emphasize strongly enough that you need to _prove_ you have a problem before you decide on a solution! Do you have any evidence that solrcloud can't handle the load you intend? Might a better approach be just to create more shards thus spreading the load and get all the HA/DR goodness of SolrCloud?
So far you've said you'll have a "heavy" load without giving us any numbers. 10,000 update/second? 10 updates/second? 1 query/second? 100,000 queries/second? 100,000 documents? 1,000,000,000,000 documents? Best Erick On Wed, Apr 3, 2013 at 5:15 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 4/3/2013 1:52 PM, Furkan KAMACI wrote: >> Thanks for your explanation, you explained every thing what I need. Just >> one more question. I see that I can not make it with Solr Cloud, but I can >> do something like that with master-slave replication of Solr. If I use >> master-slave replication of Solr, can I eliminate (filter) something >> (something that is indexed from master) from being a response after >> querying (querying from slaves) ? > > I don't understand the question. I will attempt to give you more > information, but it might not answer your question. If not, you'll have > to try to improve your question. > > Your master and each of that master's slaves will have the same index as > soon as replication is done. A query on the slave has no idea that the > master exists. > > Thanks, > Shawn >
