lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noble Paul നോബിള്‍ नोब्ळ् <>
Subject Re: Refresh synonyms.txt file via replication
Date Wed, 10 Jun 2009 04:38:31 GMT
Hi ,
Unfortunately , the problem is that an 'empty' commit does not really
do anything. I mean, it is not a real commit.Solr takes a look to find
if the index is changed and if not, the call is ignored

When we designed it, the choice was to look for all the changed conf
files also to decide if a replication is required or not . That proved
to be expensive and error prone. so we relied on index change to
trigger this.

take the case of schema.xml change . schema.xml is changed first and
then indexing is done . If the schema.xml is replicated and slave core
is reloaded , it will cause error.

you can raise an issue and we can find out a better way to do this.


On Wed, Jun 10, 2009 at 3:23 AM, mlathe<> wrote:
> Shalin Shekhar Mangar wrote:
>>> Second Question:
>>> If i force an empty commit, like this:
>>> curl
>>> http://localhost:8080/solr_rep_master/core/update?stream.body=%3Ccommit/%3E
>>> Then the changed synonym.txt config file are replicated to the slave.
>>> Unfortunately now I need to do a core "RELOAD" on both the master and
>>> slave
>>> to get them to see the updated synonym.txt file.
>> Calling RELOAD on slave should not be necessary. If a configuration file
>> is
>> replicated, the slave is always reloaded. Can you try using the
>> analysis.txt
>> on a field which has the SynonymFilterFactory enabled to see if the new
>> file
>> is indeed not getting used?
> I'm a bit confused now. It's not doing what i saw before.
> Now I can't get it to replicate when i do an "empty" commit. Rather I need
> to do a real data update, and a commit, then any changes to the
> solr_rep_master's conf/synonyms.txt file get replicated to the slave, and
> the slave seems to pick up the change without reloading.
> I'm not really sure what you mean by the analysis.txt file. Do you mean the
> /analysis request handler? I've been making synonyms for "solr" so it is
> pretty obvious if it was picked up.
> Can you explain what you expect should happen? ie
> 1) should the slave replicate when you do an empty commit on the master?
> 2) If you change a master config file, and it is replicated to the slave,
> would you expect the slave to pick it up automatically, but the master will
> require a reload?
> Thanks
> --Matthias
> --
> View this message in context:
> Sent from the Solr - User mailing list archive at

Noble Paul | Principal Engineer| AOL |

View raw message