Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of solr@elyograg.org designates
 166.70.79.219 as permitted sender)
Message-ID: <515C5954.7090405@elyograg.org>
Date: Wed, 03 Apr 2013 10:31:16 -0600
From: Shawn Heisey <solr@elyograg.org>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64;
 rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: solr-user@lucene.apache.org
Subject: Re: Filtering Search Cloud
References: 
 <CAHsXEHWDkrf7AZJUgGFOs-1dz8qRc4zrejscx_yXVNGzG_oihw@mail.gmail.com>
In-Reply-To: 
 <CAHsXEHWDkrf7AZJUgGFOs-1dz8qRc4zrejscx_yXVNGzG_oihw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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 I think that when indexing, searching make
> time to response and if I separate them I get a performance improvement. On
> the other hand maybe using all Solr machines as whole (I mean not
> partitioning as I mentioned) SolrCloud can make a better load balancing, I
> would want to learn it.
> 
> My second question is that. Let's assume that I have separated my machines
> as I mentioned. Can I filter some indexes to be searchable or not from
> Searcher SolrCloud?

SolrCloud gets rid of the master and slave designations.  It also gets
rid of the line between indexing and querying.  Each shard has a replica
that is designated the leader, but that has no real impact on searching
and indexing, only on deciding which data to use when replicas get out
of sync.

In the old master-slave architecture, you indexed to the master and the
updated index files were replicated to the slave.  The slave did not
handle the analysis for indexing, so it was usually better to send
queries to slaves and let the master only do indexing.

SolrCloud is very different.  When you index, the documents are indexed
on all replicas at about the same time.  When you query, the requests
are load balanced across all replicas.  During normal operation,
SolrCloud does not use replication at all.  The replication feature is
only used when a replica gets out of sync with the leader, and in that
case, the entire index is replicated.

Thanks,
Shawn