To the slave, a replication is more or less the same as a commit for these purposes. Can you use the newSearcher action on slave? newSearcher will happen after a replication is received.
________________________________________ From: Ophir Adiv [firt...@gmail.com] Sent: Thursday, December 09, 2010 6:34 AM To: solr-user@lucene.apache.org Subject: Triggering a reload of replicated configuration files Hi, I added a configuration file which is updated on one of the master cores' conf directory, and also added the file name to the list of "confFiles". As as expected, after index change and commit, this file gets replicated to the slave core. However, the problem that remains is how to reload this file's data after it's replicated. What I did on the master core, is to initiate a core reload, and through a custom CoreAdminHandler override handleReloadAction() to reload the new file too. But this cannot be done on the slave, since the master, which triggers the update, is unaware who is slaves are. Any ideas on how to do this? Thanks, Ophir
