I'll assume you are using the rsync-based replication, not SOLR-561.
In that case, bwlimit is your friend. You'll have to modify the scripts and
make use of this:
--bwlimit=KBPS
This option allows you to specify a maximum transfer rate in
kilobytes per second. This option is most effective
when using rsync with large files (several megabytes and up). Due
to the nature of rsync transfers, blocks of data
are sent, then if rsync determines the transfer was too fast, it
will wait before sending the next data block. The
result is an average transfer rate equaling the specified limit.
A value of zero specifies no limit.
Actually, this is something that we could add to snappuller in Solr, no?
May be worth opening a new JIRA issue for this. Eh, attaching a modified but
completely untested version of snappuller. Please reply if it works or if you
have to fix it please post it to JIRA.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
________________________________
From: oleg_gnatovskiy <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Tuesday, November 11, 2008 9:31:17 PM
Subject: Query Performance while updating the index
Hello. We have an index with 15 million documents working on a distributed
environment, with an index distribution setup. While an index on a slave
server is being updated, query response times become extremely slow (upwards
of 5 seconds). Is there any way to decrease the hit query response times
take while an index is being pushed?
Thanks!
Oleg
--
View this message in context:
http://www.nabble.com/Query-Performance-while-updating-the-index-tp20452835p20452835.html
Sent from the Solr - User mailing list archive at Nabble.com.
