You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2010/02/16 08:10:27 UTC

[jira] Issue Comment Edited: (SOLR-1775) Replication of 300MB stops indexing for 5 seconds when syncing

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

Noble Paul edited comment on SOLR-1775 at 2/16/10 7:10 AM:
-----------------------------------------------------------

The description is not clear. What do you mean by slave delays? is it that the slave does not accept any requests?

The replication has almost no perf impact on the slaves. It is an I/O bound and not CPU bound . 

      was (Author: noble.paul):
    The description is clear. What do you mean by slave delays? is it that the slave does not accept any requests?

The replication has almost no perf impact on the slaves. It is an I/O bound and not CPU bound . 
  
> 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.