[
https://issues.apache.org/jira/browse/SOLR-16879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761057#comment-17761057
]
David Smiley commented on SOLR-16879:
-------------------------------------
The solution presented is a generalized approach for any core admin command
sent with an "async" ID and that which is internally labelled as "expensive" .
> Throttle concurrent backups/restores per node
> ---------------------------------------------
>
> Key: SOLR-16879
> URL: https://issues.apache.org/jira/browse/SOLR-16879
> Project: Solr
> Issue Type: Improvement
> Components: Backup/Restore
> Affects Versions: 9.2.1
> Reporter: Pierre Salagnac
> Priority: Minor
> Time Spent: 3h
> Remaining Estimate: 0h
>
> If the collection is large enough, there very well could be many shards on
> one host and it could saturate the IO. Same issue if we backup many
> collections concurrently.
> We should have a protection mechanism, so a Solr node does not have transient
> failures during a large backup or restore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
