Ok, I will test and give you a detailed report for it, thanks for your help.
2013/4/5 Erick Erickson
> 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? Mi
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 S
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 So
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
On 4/3/2013 1:13 PM, Furkan KAMACI wrote:
> Shawn, thanks for your detailed explanation. My system will work on high
> load. I mean I will always index something and something always will be
> queried at my system. That is why I consider about physically separating
> indexer and query reply machine
Shawn, thanks for your detailed explanation. My system will work on high
load. I mean I will always index something and something always will be
queried at my system. That is why I consider about physically separating
indexer and query reply machines. I think about that: imagine a machine
that both
On 4/1/2013 3:02 PM, Furkan KAMACI wrote:
> I want to separate my cloud into two logical parts. One of them is indexer
> cloud of SolrCloud. Second one is Searcher cloud of SolrCloud.
>
> My first question is that. Does separating my cloud system make sense about
> performance improvement. Because
