Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <56B1D941.9000709@sematext.com>
References: 
 <CAF2DzVXeaGf=aYn37oOfryR=K5L0OBLycwxt-Y0w_qe4DXc+Cw@mail.gmail.com>
	<56AF3B18.4040504@sematext.com>
	<CAF2DzVXparmWRg8XRHwYhoXr4bNF4tHbLdCSibmbugx5actetw@mail.gmail.com>
	<56B0ADD6.2050804@sematext.com>
	<CAF2DzVVEumBk2z1Dhfi5fXY_84+gv9tiJxzwPYBnELKw2SvLbw@mail.gmail.com>
	<56B1D941.9000709@sematext.com>
Date: Wed, 3 Feb 2016 17:06:14 +0000
Message-ID: 
 <CAB-fSbxoj6X-_SDdZXJPLnqx2AT1za7oBtybk54iVtk83KBu=g@mail.gmail.com>
Subject: Re: Solr segment merging in different replica
From: Alessandro Benedetti <abenedetti@apache.org>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=089e015380bab300df052ae0a227

--089e015380bab300df052ae0a227
Content-Type: text/plain; charset=UTF-8

Master/Slave is the old legacy way to obtain a resilient system.
It's easier to setup, but if you are already on SolrCloud I can not see any
advantage in moving back.
Related the networking part, I am not a network expert.
The only think I can tell you is that the inter-nodes communication is
going to happen on the same REST endpoints and handlers which are used for
search/updates ( same java process).
I really doubt it is possible to have them running across different
physical network interfaces.

Cheers


On 3 February 2016 at 10:41, Emir Arnautovic <emir.arnautovic@sematext.com>
wrote:

> Hi Edwin,
> Master-Slave's main (maybe only) advantage is simpler infrastructure - it
> does not use ZK. Also, it does assume you don't need NRT search since there
> has to be longer periods between replicating master changes to slaves.
>
> Regards,
> Emir
>
>
> On 03.02.2016 04:48, Zheng Lin Edwin Yeo wrote:
>
>> Hi Emir,
>>
>> Thanks for your reply.
>>
>> As currently both of my main and replica are in the same server, and as I
>> am using the SolrCloud setup, both the replica are doing the merging
>> concurrently, which causes the memory usage of the server to be very high,
>> and affect the other functions like querying. This issue should be
>> eliminated when I shift my replica to another server.
>>
>> Would like to check, will there be any advantage if I change to the
>> Master-Slave setup, as compared to the SolrCloud setup which I am
>> currently
>> using?
>>
>> Regards,
>> Edwin
>>
>>
>>
>> On 2 February 2016 at 21:23, Emir Arnautovic <
>> emir.arnautovic@sematext.com>
>> wrote:
>>
>> Hi Edwin,
>>> Do you see any signs of network being bottleneck that would justify such
>>> setup? I would suggest you monitor your cluster before deciding if you
>>> need
>>> separate interfaces for external and internal communication. Sematext's
>>> SPM
>>> (http://sematext.com/spm) allows you to monitor SolrCloud, hosts and
>>> network and identify bottlenecks in your cluster.
>>>
>>> Regards,
>>> Emir
>>>
>>> --
>>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>>> Solr & Elasticsearch Support * http://sematext.com/
>>>
>>>
>>>
>>> On 02.02.2016 00:50, Zheng Lin Edwin Yeo wrote:
>>>
>>> Hi Emir,
>>>>
>>>> My setup is SolrCloud.
>>>>
>>>> Also, will it be good to use a separate network interface to connect the
>>>> two node with the interface that is used to connect to the network for
>>>> searching?
>>>>
>>>> Regards,
>>>> Edwin
>>>>
>>>>
>>>> On 1 February 2016 at 19:01, Emir Arnautovic <
>>>> emir.arnautovic@sematext.com>
>>>> wrote:
>>>>
>>>> Hi Edwin,
>>>>
>>>>> What is your setup - SolrCloud or Master-Slave? If it si SolrCloud,
>>>>> then
>>>>> under normal index updates, each core is behaving as independent index.
>>>>> In
>>>>> theory, if all changes happen at the same time on all nodes, merges
>>>>> will
>>>>> happen at the same time. But that is not realistic and it is expected
>>>>> to
>>>>> happen in slightly different time.
>>>>> If you are running Master-Slave, then new segments will be copied from
>>>>> master to slave.
>>>>>
>>>>> Regards,
>>>>> Emir
>>>>>
>>>>> --
>>>>> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
>>>>> Solr & Elasticsearch Support * http://sematext.com/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 01.02.2016 11:56, Zheng Lin Edwin Yeo wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>> I would like to check, during segment merging, how did the replical
>>>>>> node
>>>>>> do
>>>>>> the merging?
>>>>>> Will it do the merging concurrently, or will the replica node delete
>>>>>> the
>>>>>> old segment and replace the new one?
>>>>>>
>>>>>> Also, is it possible to separate the network interface for inter-node
>>>>>> communication from the network interface for update/search requests?
>>>>>> If so I could put two network cards in each machine and route the
>>>>>> index
>>>>>> and
>>>>>> search traffic over the first interface and the traffic for the
>>>>>> inter-node
>>>>>> communication (sending documents to replicas) over the second
>>>>>> interface.
>>>>>>
>>>>>> I'm using Solr 5.4.0
>>>>>>
>>>>>> Regards,
>>>>>> Edwin
>>>>>>
>>>>>>
>>>>>>
>>>>>>
> --
> Monitoring * Alerting * Anomaly Detection * Centralized Log Management
> Solr & Elasticsearch Support * http://sematext.com/
>
>


-- 
--------------------------

Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti

"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"

William Blake - Songs of Experience -1794 England

--089e015380bab300df052ae0a227--