[
https://issues.apache.org/jira/browse/SOLR-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875808#comment-16875808
]
Steve Loughran commented on SOLR-9952:
--------------------------------------
[~mkhludnev] is right: listings are one of the worst cases of eventual
consistency
* Manifest files avoid this, though if backups involve overwriting the previous
manifest, you are at risk of eventual consistency problems here.
* You can actually switch to an "inconsistent s3 client" underneath the S3A
connector which simulates delayed list consistency (duration, probability of
occurrence)...it allows you to verify resilience to listing inconsistencies by
guaranteeing that test runs will encounter the problem. We use it a lot in
integration testing of the S3Guard consistency layer: even in the presence of
list problems, you still get a consistent view
> S3BackupRepository
> ------------------
>
> Key: SOLR-9952
> URL: https://issues.apache.org/jira/browse/SOLR-9952
> Project: Solr
> Issue Type: New Feature
> Components: Backup/Restore
> Reporter: Mikhail Khludnev
> Priority: Major
> Attachments:
> 0001-SOLR-9952-Added-dependencies-for-hadoop-amazon-integ.patch,
> 0002-SOLR-9952-Added-integration-test-for-checking-backup.patch, Running Solr
> on S3.pdf, core-site.xml.template
>
>
> I'd like to have a backup repository implementation allows to snapshot to AWS
> S3
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
