[
https://issues.apache.org/jira/browse/SOLR-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969455#action_12969455
]
McClain Looney commented on SOLR-1775:
--------------------------------------
We are definitely not holding our data on another partition (as far as i can
tell). interestingly, replication.properties seems to show that we had several
failures right around the time of our last "brown out":
#Replication details
#Wed Dec 08 13:40:00 CST 2010
replicationFailedAtList=1291826400058,1291826100059,1291825800087,1291825500059,1291825200109,1291485000059,1291484700058,1291484400061,1291484100042
previousCycleTimeInSeconds=0
timesFailed=9
indexReplicatedAtList=1291837200673,1291836911689,1291834200139,1291826700131,1291826400058,1291826100059,1291825800087,1291825500059,1291825200109,1291824302091
indexReplicatedAt=1291837200673
replicationFailedAt=1291826400058
timesIndexReplicated=274
lastCycleBytesDownloaded=11327528
our index is about 17gb, our largest segment is 5.0gb
> 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: [email protected]
For additional commands, e-mail: [email protected]
