Amit Nithian created SOLR-4354:
----------------------------------
Summary: Replication should perform full copy if slave's
generation higher than master's
Key: SOLR-4354
URL: https://issues.apache.org/jira/browse/SOLR-4354
Project: Solr
Issue Type: Bug
Components: replication (java)
Affects Versions: 4.1
Reporter: Amit Nithian
Fix For: 4.2
Attachments: SOLR-4354.patch
We have dual masters each incrementally indexing from our MySQL database and
sit behind a virtual hostname in our load balancer. As such, it's possible that
the generation numbers between the masters for a given index are not in sync.
Slaves are configured to replicate from this virtual host (and pin based on
source/dest IP hash) so we can add and remove masters as necessary (great for
maintenance).
For the most part this works but we've seen the following happen:
* Slave has been pulling from master A
* Master A goes down for maint and now will pull from master B (which has a
lower generation number for some reason than master A).
* Slave now tries to pull from master B (has higher index version than slave
but lower generation).
* Slave downloads index files, moves them to the index/ directory but these
files are deleted during the doCommit() phase (looks like older generation data
is deleted).
* Index remains as-is and no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
