On Sat, Jun 13, 2009 at 1:25 AM, Phil Hagelberg <p...@hagelb.org> wrote:
> > OK, so I inserted some more documents into the master, and now > replication works. I get the feeling it may be due to this line in the > master's solrconfig.xml: > > <str name="replicateAfter">commit</str> > > Now this is confusing since it seems that the timing of replication is > not up to the master, it's up to the slave. The slave's config has > settings for the interval at which to replicate, and you POST to the > slave to force a replication. So why is there a setting on the master to > control when replication happens? > > My only interpretation from the config files is the master has some sort > of "you may not replicate from me unless" conditions. This seems pretty > undesirable since you may have a slave that needs to get replicated from > the master immediately; it shouldn't have to wait for a commit on the > master. Am I misunderstanding what's going on here? It certainly isn't > clear from the documents on the wiki, so I'm kind of grasping in the > dark. Perhaps I'm missing something. > > You are right. In Solr/Lucene, a commit exposes updates to searchers. So you need to call commit on the master for the slave to pick up the changes. Replicating changes from the master and then not exposing new documents to searchers does not make sense. However, there is a lot of work going on in Lucene to enable near real-time search (exposing documents to searchrs as soon as possible). Once those features are mature enough, Solr's replication will follow suit. -- Regards, Shalin Shekhar Mangar.
