mchennupati commented on issue #726:
URL: https://github.com/apache/solr-operator/issues/726#issuecomment-2532382503
Thank you for your reply. Yes, I think i didnt quite understand how the
restore worked, but i figured it out eventually.
One aspect of my question still remains, perh
gerlowskija closed issue #726: Solr Restore Space Considerations in Kubernetes
URL: https://github.com/apache/solr-operator/issues/726
--
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 com
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 relate
mchennupati opened a new issue, #726:
URL: https://github.com/apache/solr-operator/issues/726
I am restoring a large index (655G) that is currently on google cloud
storage to a new solr cloud on kubernetes instance. I am trying to understand
how much space I need to allocate to each of my
