You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Amit Nithian (JIRA)" <ji...@apache.org> on 2013/01/25 18:39:12 UTC
[jira] [Closed] (SOLR-4354) Replication should perform full copy if
slave's generation higher than master's
[ https://issues.apache.org/jira/browse/SOLR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Nithian closed SOLR-4354.
------------------------------
Resolution: Invalid
My apologies that was embarrassing. I was looking at the 4.0 code that we use and not the 4.1 code which has this fixed. I blindly copied my code to trunk without doing a proper code refresh (so much for late night working).
Again please accept my apologies.
> 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
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org