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

Ramkumar Aiyengar edited comment on SOLR-6485 at 9/15/14 1:05 PM:
------------------------------------------------------------------

You still need the 10s commit reservation. The reason being, replication 
happens like this:

 - Replica gets list of files from leader
 - For each file, replica fetches the file from leader

After the first step happens, you need to keep the commit alive for the entire 
duration of the second step which involves many, many requests. So you need to 
keep extending the commit reservation between requests. I think the 
save/release is clean for the duration of the write, you probably still need 
the older release at the end of it..


was (Author: andyetitmoves):
You still need the 10s commit. The reason being, replication happens like this:

 - Replica gets list of files from leader
 - For each file, replica fetches the file from leader

After the first step happens, you need to keep the commit alive for the entire 
duration of the second step which involves many, many requests. So you need to 
keep extending the commit reservation between requests. I think the 
save/release is clean for the duration of the write, you probably still need 
the older release at the end of it..

> ReplicationHandler should have an option to throttle the speed of replication
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-6485
>                 URL: https://issues.apache.org/jira/browse/SOLR-6485
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Varun Thacker
>            Assignee: Noble Paul
>         Attachments: SOLR-6485.patch, SOLR-6485.patch, SOLR-6485.patch, 
> SOLR-6485.patch
>
>
> The ReplicationHandler should have an option to throttle the speed of 
> replication.
> It is useful for people who want bring up nodes in their SolrCloud cluster or 
> when have a backup-restore API and not eat up all their network bandwidth 
> while replicating.
> I am writing a test case and will attach a patch shortly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to