Thanks, that issue looks interesting!

On 16/12/16 16:38, Pushkar Raste wrote:
> This kind of separation is not supported yet.  There however some work
> going on,  you can read about it on
> https://issues.apache.org/jira/browse/SOLR-9835
> 
> This unfortunately would not support soft commits and hence would not be a
> good solution for near real time indexing.
> 
> On Dec 16, 2016 7:44 AM, "Jaroslaw Rozanski" <m...@jarekrozanski.com> wrote:
> 
>> Sorry, not what I meant.
>>
>> Leader is responsible for distributing update requests to replica. So
>> eventually all replicas have same state as leader. Not a problem.
>>
>> It is more about the performance of such. If I gather correctly normal
>> replication happens by standard update request. Not by, say, segment copy.
>>
>> Which means update on leader is as "expensive" as on replica.
>>
>> Hence, if my understanding is correct, sending search request to replica
>> only, in index heavy environment, would bring no benefit.
>>
>> So the question is: is there a mechanism, in SolrCloud (not legacy
>> master/slave set-up) to make one node take a load of indexing which
>> other nodes focus on searching.
>>
>> This is not a question of SolrClient cause that is clear how to direct
>> search request to specific nodes. This is more about index optimization
>> so that certain nodes (ie. replicas) could suffer less due to high
>> volume indexing while serving search requests.
>>
>>
>>
>>
>> On 16/12/16 12:35, Dorian Hoxha wrote:
>>> The leader is the source of truth. You expect to make the replica the
>>> source of truth or something???Doesn't make sense?
>>> What people do, is send write to leader/master and reads to
>> replicas/slaves
>>> in other solr/other-dbs.
>>>
>>> On Fri, Dec 16, 2016 at 1:31 PM, Jaroslaw Rozanski <m...@jarekrozanski.com
>>>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> According to documentation, in normal operation (not recovery) in Solr
>>>> Cloud configuration the leader sends updates it receives to all the
>>>> replicas.
>>>>
>>>> This means and all nodes in the shard perform same effort to index
>>>> single document. Correct?
>>>>
>>>> Is there then a benefit to *not* to send search requests to leader, but
>>>> only to replicas?
>>>>
>>>> Given index & search heavy Solr Cloud system, is it possible to separate
>>>> search from indexing nodes?
>>>>
>>>>
>>>> RE: Solr 5.5.0
>>>>
>>>> --
>>>> Jaroslaw Rozanski | e: m...@jarekrozanski.com
>>>> 695E 436F A176 4961 7793  5C70 AFDF FB5E 682C 4D3D
>>>>
>>>>
>>>
>>
>> --
>> Jaroslaw Rozanski | e: m...@jarekrozanski.com
>> 695E 436F A176 4961 7793  5C70 AFDF FB5E 682C 4D3D
>>
>>
> 

-- 
Jaroslaw Rozanski | e: m...@jarekrozanski.com
695E 436F A176 4961 7793  5C70 AFDF FB5E 682C 4D3D

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to