a Gong <pla.g...@kibocommerce.com>
> Sent: Monday, April 25, 2016 9:27 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr slave is doing full replication (entire index) of index
> after master restart
>
> Please remove me from the newsgroup.
>
> Thanks,
>
r-user@lucene.apache.org
Subject: Re: Solr slave is doing full replication (entire index) of index after
master restart
Please remove me from the newsgroup.
Thanks,
Pla
From: Shalin Shekhar Mangar <shalinman...@gmail.com>
Sent: Monday, April 25, 2016 8:20 AM
T
Please remove me from the newsgroup.
Thanks,
Pla
From: Shalin Shekhar Mangar <shalinman...@gmail.com>
Sent: Monday, April 25, 2016 8:20 AM
To: solr-user@lucene.apache.org
Cc: lior.sa...@gmail.com
Subject: Re: Solr slave is doing full replication (
Hi Lior,
Sorry for the late reply. I am able to successfully reproduce this problem
on Solr 5.3.1 and on Solr 6.0.0 as well.
The interesting thing is that if the master is restarted before the poll
interval (1 minute in your case) then the index is not downloaded again.
But if the slave makes
So what do you say:
Is it a problem in my environment + confs
OR
That's how the replication is working
(if a slave fails to locate the master when polling then next time the
master is available it will replicate the entire index even if no document
was added to the master and no optimization was
Thanks for the reply.
00:00:60 - Is valid
But I tried 00:01:00 anyway.
I also checked the clocks and they are synced:
ntpdate -q solr01-isrl01
server 192.168.103.112, stratum 11, offset 0.003648, delay 0.02589
9 Apr 18:09:20 ntpdate[23921]: adjust time server 192.168.103.112 offset
0.003648 sec
I’m not sure this is a legal polling interval:
00:00:60
Try:
00:01:00
Also, polling every minute is very fast. Try a longer period.
Check the clocks on the two systems. If the clocks are not synchronized, that
could cause problem.
wunder
Walter Underwood
Anyone can tell me what was I doing wrong ?
Is that the expected behavior (slave replicate entire index if on previous
replication attempt the master was not available ) ?
On Thu, Apr 7, 2016 at 9:12 PM, Lior Sapir wrote:
> Thanks for the reply.
>
> I easily re produced
Thanks for the reply.
I easily re produced it in my "sandbox" env. Steps to re produce
1. Setup a master
2. Setup a slave in a different server
3. The slave replicated the master index
4. From now on not even a single document is added. No optimization or what
so ever is done on the master or
What does your configuration file look like for the replication
handler? Does this happen whenever you restart a slave even if
_nothing_ has changed on the master?
And this will certainly happen if you're optimizing the master before
you restart, although that doesn't sound likely.
Best,
Erick
10 matches
Mail list logo