hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Fabbri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13345) S3Guard: Improved Consistency for S3A
Date Sat, 18 Feb 2017 01:50:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872867#comment-15872867

Aaron Fabbri commented on HADOOP-13345:

Thanks [~liuml07]!

$ mvn -Dit.test='ITestS3A*' -Dscale -Dtest=none -Ds3guard -Ddynamo -q clean verify
Thats ok.. It does miss ITestS3Guard{ListConsistency, ToolDynamoDB}, FYI, but you got most
of the tests.

2. ITestS3ACredentialsInURL#testInstantiateFromURL is not supported. Should we simply skip
this test if the metadata store is enabled (in a separate JIRA)?

Yes.  Nothing new here and we do need to fix it.

3. ITestS3AEncryptionSSEC started failing after merge because of the strict exception message
assertion; it is fine in trunk. The only change is to remove "Forbidden" word as it would
be "Access Denied" sometimes along with the same exception class java.nio.file.AccessDeniedException
and message Service: Amazon S3; Status Code: 403; Error Code: AccessDenied;. For this I made
the change when merging.

Sounds ok.  Curious, what is our difference in HADOOP-13345 that changes this?  Is our feature
branch exception behavior different?

> S3Guard: Improved Consistency for S3A
> -------------------------------------
>                 Key: HADOOP-13345
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13345
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-13345.prototype1.patch, s3c.001.patch, S3C-ConsistentListingonS3-Design.pdf,
S3GuardImprovedConsistencyforS3A.pdf, S3GuardImprovedConsistencyforS3AV2.pdf
> This issue proposes S3Guard, a new feature of S3A, to provide an option for a stronger
consistency model than what is currently offered.  The solution coordinates with a strongly
consistent external store to resolve inconsistencies caused by the S3 eventual consistency

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message