gerlowskija commented on issue #726: URL: https://github.com/apache/solr-operator/issues/726#issuecomment-2532364686
(Hi @mchennupati - it looks like the formatting on your post mangled a few things, so apologies if I'm missing something.) afaict your question isn't necessarily related to using the operator for restores, it's just a question about the disk and network costs of restoring a Solr collection? Assuming I've got that right - a better place to ask in the future would be our project's "user" mailing list: us...@solr.apache.org. Please subscribe and ask similar questions there going forward! To your specific question: if you're restoring data to an existing collection, Solr will have each replica fetch data from the backup repository. (So if you have three replicas each fetching a 100gb index, you'll pull 300gb from GCS). Restores to a new collection work slightly differently, with only one replica fetching the index and then distributing it within your Solr cluster as needed. So the network impact of restores can be tuned a little bit. In terms of disk space though - ultimately all replicas of a shard will need a full copy of that shard's data, which sounds like 665GB in your case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
