lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Forcing config replication without index change
Date Thu, 16 Jul 2009 15:00:27 GMT

Hi,

Shouldn't it be possible to force replication of at least *some* of the config files even
if the index hasn't changed?
(see Paul Noble's comment on http://markmail.org/message/hgdwumfuuwixfxvq and the 4-message
thread)

Here is a use case:
* Index is mostly static (nightly updates)
* elevate.xml needs to be changed throughout the day
* elevate.xml needs to be pushed to slaves and solr needs to reload it

This is currently not possible because replication will happen only if the index changed in
some way.  You can't force a commit to fake index change.  So one has to either:
* add/delete dummy docs on master to force index change
* write an external script that copies the config file to slaves


Shouldn't it be possible to force replication of at least *some* of the config files even
if the index hasn't changed?

Thanks,
Otis 
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch


Mime
View raw message