Re: Solr segment merging in different replica

2016-02-04 Thread Zheng Lin Edwin Yeo
Hi Shawn, Thanks for your reply. Yes, we were planning for such instance where the replica went down during indexing, and when it re-started, it will start to copy the index over to the main node. Regards, Edwin On 5 February 2016 at 03:35, Shawn Heisey wrote: > On 2/4/2016 9:27 AM, Zheng L

Re: Solr segment merging in different replica

2016-02-04 Thread Shawn Heisey
On 2/4/2016 9:27 AM, Zheng Lin Edwin Yeo wrote: > Yes, I'm already on SolrCloud, so I'll probably stick to that. > > Regarding the network, I am just afraid that when the replica code copies > the index over from the main node, it will use up all the available > bandwidth, and causes the search que

Re: Solr segment merging in different replica

2016-02-04 Thread Zheng Lin Edwin Yeo
Thanks Emir and Benedetti. Yes, I'm already on SolrCloud, so I'll probably stick to that. Regarding the network, I am just afraid that when the replica code copies the index over from the main node, it will use up all the available bandwidth, and causes the search query to have little bandwidth l

Re: Solr segment merging in different replica

2016-02-03 Thread Alessandro Benedetti
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

Re: Solr segment merging in different replica

2016-02-03 Thread Emir Arnautovic
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:

Re: Solr segment merging in different replica

2016-02-02 Thread Zheng Lin Edwin Yeo
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. T

Re: Solr segment merging in different replica

2016-02-02 Thread Emir Arnautovic
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,

Re: Solr segment merging in different replica

2016-02-01 Thread Zheng Lin Edwin Yeo
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 wrote: > Hi Edwin, > What is your setup - Sol

Re: Solr segment merging in different replica

2016-02-01 Thread Emir Arnautovic
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 ex

Solr segment merging in different replica

2016-02-01 Thread Zheng Lin Edwin Yeo
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 n