[
https://issues.apache.org/jira/browse/HADOOP-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Fabbri updated HADOOP-13793:
----------------------------------
Attachment: HADOOP-13793-HADOOP-13345.003.patch
Attaching v3 patch addressing [~liuml07]'s comments.
- Increase inconsistency time period 10 x from 0.5 seconds to 5.0 seconds.
- Don't hard code LocalMetadataStore in ITestS3GuardListInconsistency: Besides
testing s3a logic is correct, other MetadataStores may wish to integration test
with this as well.
- Skip the inconsistency test if NullMetadataStore is enabled (it would fail).
- Clean up duplicate comment and no-op method overrides.
> s3guard: add inconsistency injection, integration tests
> -------------------------------------------------------
>
> Key: HADOOP-13793
> URL: https://issues.apache.org/jira/browse/HADOOP-13793
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Aaron Fabbri
> Assignee: Aaron Fabbri
> Attachments: HADOOP-13793-HADOOP-13345.001.patch,
> HADOOP-13793-HADOOP-13345.002.patch, HADOOP-13793-HADOOP-13345.003.patch
>
>
> Many of us share concerns that testing the consistency features of S3Guard
> will be difficult if we depend on the rare and unpredictable occurrence of
> actual inconsistency in S3 to exercise those code paths.
> I think we should have a mechanism for injecting failure to force exercising
> of the consistency codepaths in S3Guard.
> Requirements:
> - Integration tests that cause S3A to see the types of inconsistency we
> address with S3Guard.
> - These are deterministic integration tests.
> Unit tests are possible as well, if we were to stub out the S3Client. That
> may be less bang for the buck, though.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
