Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 5 Jan 2017 02:01:01 +0000 (UTC)
From: "Aaron Fabbri (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12987291.1467840223000.645897.1483581661866@Atlassian.JIRA>
In-Reply-To: <JIRA.12987291.1467840223000@Atlassian.JIRA>
References: <JIRA.12987291.1467840223000@Atlassian.JIRA> <JIRA.12987291.1467840223268@arcas>
Subject: [jira] [Commented] (HADOOP-13345) S3Guard: Improved Consistency for
 S3A
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 05 Jan 2017 02:01:03 -0000


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

Aaron Fabbri commented on HADOOP-13345:
---------------------------------------

Thanks for your input [~liuml07].  The reason I propose doing the retry logic after merge is:

1. It will change S3AFileSystem code significantly.  At least in terms of dealing with merge conflicts, things like putting a function inside a retry loop (increasing the indent of all the code) might mean a good amount of code churn.

2. I'm not sure retries are needed for basic list consistency.  The failure injection test I added demonstrates that basic listing consistency works.  Since most S3 GETs are consistent, I would expect use cases like PUT, list, GET to work as is.

Let me know if I'm missing something.  Looking forward to others' opinions too.  Cheers!


> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org