Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Message-ID: <14355832.21961291837142534.JavaMail.jira@thor>
Date: Wed, 8 Dec 2010 14:39:02 -0500 (EST)
From: "Mark Miller (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1775) Replication of 300MB stops indexing
 for 5 seconds when syncing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969446#action_12969446 ] 

Mark Miller commented on SOLR-1775:
-----------------------------------

Backup copies, but if I remember right, the java replication handler will attempt to rename - if that fails (going across drives/partitions), it does a copy?

> Replication of 300MB stops indexing for 5 seconds when syncing
> --------------------------------------------------------------
>
>                 Key: SOLR-1775
>                 URL: https://issues.apache.org/jira/browse/SOLR-1775
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 1.4
>         Environment: Centos 5.3
>            Reporter: Bill Bell
>
> When using Java replication in v1.4 and doing a sync from master to slave, the slave delays for about 5-10 seconds. When using rsync this does not occur.
> Is there a way to thread better or lower the priority to not impact queries when it is bringing over the index files from the master? Maybe a separate process?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org