To answer your first question, yes, the S3BackupRepository connects directly to S3. There is no need to have any shared storage. The next version of the Solr Operator (v0.5.0) will actually make this very easy to enable on Kubernetes clusters, such as EKS.
I am not sure about the answer to your second question. - Houston On Thu, Oct 14, 2021 at 4:00 AM Tomer Y. <[email protected]> wrote: > Hello, > > This is the first time I send a message to this User List, any help will be > appreciated, we're also open for (paid) consultancy. > > We are looking to deploy SolrCloud 8.10 into an EKS cluster > Normally, you'd need a shared volume between all Solr nodes - because every > node/pod needs access to the data being restored. This can be solved using > any NFS (EFS or File Gateway) or replicating an EBS volume per number of > nodes in the cluster and attached one to each > > My question is if it's possible using the S3BackupRepository to skip having > the need to use EFS/File Gateway and have each Solr node communicate > directly with S3 > > If the answer is yes, then a followup question: our backup is about 5TB. > Does this means that each of the nodes in the cluster will need to fetch > 5TB from S3? > > > > Thank you >
