If you use LocalReplicator on both sides, you have to use the same instance on both sides. Otherwise the replicas will never see the published revisions the which are done in a separate instance. Can you try that?
Shai On Mar 15, 2014 1:10 PM, "Roberto Franchini" <franch...@celi.it> wrote: > On Sat, Mar 15, 2014 at 11:58 AM, Michael McCandless > <luc...@mikemccandless.com> wrote: > > I think maybe the problem is you are using LocalReplicator on the > > replicas? I think you should only use that on the master. I think > > e.g. you should use HttpReplicator on the clients? Or, your own > > implementation that moves the files its own way. > > > > Have you seen Shai's blog post about this? > > http://shaierera.blogspot.com/2013/05/the-replicator.html > > Yes, I've seen it. I checkout the replicator code and looked at test code. > > I'm trying to use the local replicator because, as a first step, I > want only to incrementally backup indexes. > > So I've implemented a sort of producer/consumer where the indexer is > the producer, it runs on it's own thread and publish revisions, and > the consumer will be the replicator client that's on it's onw thread. > > Code samples aren't, at least for me, very clear in how to use the > replicator. > So, if someone has a clean sample of use of replicator I would appreciate > it. > > REgards, > RF > > -- > Roberto Franchini > The impossible is inevitable. > http://www.celi.it http://www.blogmeter.it > http://github.com/celi-uim http://github.com/robfrank > Tel +39.011.562.71.15 > jabber:ro.franch...@gmail.com skype:ro.franchini tw:@robfrankie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
