> up for after
>
> -Kevin
>
> From: users@solr.apache.org At: 07/30/24 13:20:35 UTC-4:00To:
> users@solr.apache.org
> Subject: Re: Collection Backup API
>
> Thanks Kevin! Have you used the Restore API? If so, do you restore to
> the current SolrCloud or to a new SolrCloud instanc
additional restore requests sent during that
time won't trigger multiple concurrent jobs but will queue up for after
-Kevin
From: users@solr.apache.org At: 07/30/24 13:20:35 UTC-4:00To:
users@solr.apache.org
Subject: Re: Collection Backup API
Thanks Kevin! Have you used the Restore API?
queries at the same time as backup will noticeably
> increase CPU usage (backup by itself will use around 1-2 cores worth of CPU
> cycles)
>
> From: users@solr.apache.org At: 07/26/24 11:51:13 UTC-4:00To:
> users@solr.apache.org
> Subject: Re: Collection Backup API
>
> Looks l
ies at the same time as backup will noticeably increase CPU
usage (backup by itself will use around 1-2 cores worth of CPU cycles)
From: users@solr.apache.org At: 07/26/24 11:51:13 UTC-4:00To:
users@solr.apache.org
Subject: Re: Collection Backup API
Looks like I found the answer -
https://solr.a
Looks like I found the answer -
https://solr.apache.org/guide/solr/latest/deployment-guide/backup-restore.html#backup-api
:
The backup command is an asynchronous call, and it will represent data from
> the latest index commit point. All indexing and search operations will
> continue to be executed
And the same question for the Snapshot API -
https://solr.apache.org/guide/solr/latest/deployment-guide/backup-restore.html#create-snapshot-api
On Fri, Jul 26, 2024 at 9:28 AM mtn search wrote:
> Hello,
>
> Does the Backup API -
> https://solr.apache.org/guide/solr/latest/deployment-guide/collec
