Yes. However, something must actually have been updated in the index before a commit on the master causes the slave to update (this is what was confusing me).
Since I'll be updating the index fairly often, this will not be a problem for me. If, however, the external file field is updated often, but the index proper isn't, this could be a problem. Thanks, /Martin On Thu, Jan 5, 2012 at 2:56 PM, Erick Erickson <erickerick...@gmail.com>wrote: > Hmmm, does it work just to put this in the masters index and let > replication to its tricks and issue your commit on the master? > > Or am I missing something here? > > Best > Erick > > On Tue, Jan 3, 2012 at 1:33 PM, Martin Koch <m...@issuu.com> wrote: > > Hi List > > > > I have a Solr cluster set up in a master/slave configuration where the > > master acts as an indexing node and the slaves serve user requests. > > > > To avoid accidental posts of new documents to the slaves, I have disabled > > the update handlers. > > > > However, I use an externalFileField. When the file is updated, I need to > > issue a commit to reload the new file. This requires an update handler. > Is > > there an update handler that doesn't accept new documents, but will > effect > > a commit? > > > > Thanks, > > /Martin >
