OK, probably this is what's happening: There's no event that causes
the slave to say "Oh, my index is out of date". This assumes (and I
haven't checked) that you have the same number of segments etc.
after the upgrade to 4x format.
So when you update a doc, that registers a "change event" that the
Erick
My apologies,if I was rushing. Yes its' an old style master/slave
replication. I was going through solr logs, but don't see any errors as
such. The slave are correctly configured and pointing to master
correctly, one thing I noted is on creating any new document to the
master, its get
You have to be a bit patient. Folks in the US, at least, are barely awake yet.
We are not a paid-support helpdesk...
On to your problem. You haven't given enough information to say much. for
instance, what do you mean by "replication"? Old-style master/slave replication?
Do you see any errors in y
Folks, any response to below query would be highly appreciated
Thanks,
Anand
On 1/10/2014 11:04 AM, anand chandak wrote:
Hi,
I am testing replication feature of solr 4.x with large index,
unfortunately, that index that we had was 3.x format. So to conver
that into 4.x I copied (file sys
gt; To: solr-user@lucene.apache.org
> Sent: Thu, October 7, 2010 5:55:16 PM
> Subject: RE: Copying index to another server
>
> You can simply copy the data folder into the new instance, making sure
> the conf folder has the same schema.xml configuration file first of
> course.
&g
You can simply copy the data folder into the new instance, making sure
the conf folder has the same schema.xml configuration file first of
course.
-Original Message-
From: Parsa Ghaffari [mailto:parsa.ghaff...@gmail.com]
Sent: Wednesday, October 06, 2010 11:44 PM
To: solr-user@lucene.apac
