On 5/14/10 8:08 PM, Chris Hostetter wrote:
: It looks like SnapPuller.java doesn't allow for the possibility of the
: slave having a later index version than the master. It only checks
: whether the versions are equal.
:
: It's easy enough to add that check and prevent the index fetch when
: the slave has a later version (in fact I'm running it in a sandbox
I'm not 100% positive, but i believe a change like that could cause
problems if the index on the master is completley rebuild from scratch.
indexVersion is garunteed to increase as the index is modified, (ie: add
or merge segments) but i think an entirely new index (ie: delete the
entire index directory as deleteByQuery("*:*) does and then reindex) could
concievably result i na new index with a lower indexVersion number then
the index it replaces.
I think you should be good because the version starts as the current
time in milliseconds? (and then is incremented by 1 on every commit
thereafter)
Yonik / Miller: does the SolrCloud branch already have support for master
failover in a situation like this (ie: a two node "cloud") ?
No - no master/failover support in SolrCloud yet. We havn't integrated
at all with replication yet.
-Hoss
--
- Mark
http://www.lucidimagination.com
