lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zheng Lin Edwin Yeo <edwinye...@gmail.com>
Subject Re: Solr segment merging in different replica
Date Wed, 03 Feb 2016 03:48:41 GMT
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
>>>>
>>>>
>>>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message