[
https://issues.apache.org/jira/browse/SOLR-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-6485:
--------------------------------
Attachment: SOLR-6485.patch
{quote}
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
{quote}
Right nice catch!
So this is what the new patch does -
1. Saves the commit point for the duration of the write. We will not loose the
commit point no matter how much the user throttles.
2. At the end of the write it extends it by 10s so that the commit point is
reserved across file fetches
3. Added an extra condition to the test case - I add extra docs to the master
after I call replicate. These docs should not be reflected in the slave server.
> 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, 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]
