[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801537#comment-15801537
]
Steve Loughran commented on HADOOP-13345:
-----------------------------------------
I'd like to see manageability, correctness and maintainability, especially to
the extent that we are confident that people can start to play with it and not
get into a mess.
This means: that CLI is usable, documented, tested. I think we need some fsck
option to verify that everything matches between DB and FS, fsck --fix to do
the corrections.
Other management? Some metrics, consistent with the rest of the S3A metrics, in
terms of what they count, and appearing in S3AFileSystem.toString for some
diagnostics downstream
maintainability: let's look at the code and see if its integration with S3A is
as clean as we can have it. Once you have things merged into trunk and two
branches forking again, it becomes much harder to clean up.
> 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-ConsistentListingonS3-Design.pdf, S3GuardImprovedConsistencyforS3A.pdf,
> S3GuardImprovedConsistencyforS3AV2.pdf, s3c.001.patch
>
>
> 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 model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
