Not OOB. You say that the index updates, but if the data hasn't been committed, it isn't really in the index. After the commit (which varies time-wise depending on merges etc.) the next replication from the slave should get the new index, regardless of whether the master has gone down or not.
One way to handle this issue is to re-index data from some time before the master went down, relying on the uniqueKey to replace any duplicate documents.... Best Erick On Wed, Jul 27, 2011 at 10:43 AM, Nagendraprasad <nagu.nutalap...@gmail.com> wrote: > Suppose master goes down immediately after the index updates, while the > updates haven't been replicated to the slaves, data loss seems to happen. > Does Solr have any mechanism to deal with that? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Master-slave-master-failover-without-data-loss-tp3203644p3203644.html > Sent from the Solr - User mailing list archive at Nabble.com. >
