[
https://issues.apache.org/jira/browse/HADOOP-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925119#comment-15925119
]
Aaron Fabbri commented on HADOOP-13345:
---------------------------------------
{quote}What about the prefix "s3guard+" on all buckets unless otherwise
stated?{quote}
We generally try to discourage the per-bucket DDB table naming, as customers
with jobs that access multiple buckets can end up with a slew of DDB tables,
and it is a waste to provision them each for peak load.
We generally try to do one DDB table per cluster, with optional sharing between
clusters. I'm leaning towards a default name "s3guard-metadata" which is
populated above Hadoop (i.e. CM or Ambari).
Personally I'd suggest not bothering too much with the per-bucket case.
> 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 model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
