Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AE055E2CB for ; Fri, 25 Jan 2013 07:25:17 +0000 (UTC) Received: (qmail 40570 invoked by uid 500); 25 Jan 2013 07:25:16 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 40235 invoked by uid 500); 25 Jan 2013 07:25:15 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 40168 invoked by uid 99); 25 Jan 2013 07:25:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2013 07:25:12 +0000 Date: Fri, 25 Jan 2013 07:25:12 +0000 (UTC) From: "Amit Nithian (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SOLR-4354) Replication should perform full copy if slave's generation higher than master's MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org