[jira] [Commented] (HADOOP-14468) S3Guard: make short-circuit getFileStatus() configurable

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on HADOOP-14468:
-----------------------------------------

FWIW not doing the unshort-circuited check will save $0.004 $0.01.3 c/open() call in the case the file is missing; $0.004 if the file is actually there

> S3Guard: make short-circuit getFileStatus() configurable
> --------------------------------------------------------
>
>                 Key: HADOOP-14468
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14468
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0-beta1
>            Reporter: Aaron Fabbri
>            Assignee: Aaron Fabbri
>            Priority: Minor
>
> Currently, when S3Guard is enabled, getFileStatus() will skip S3 if it gets a result from the MetadataStore (e.g. dynamodb) first.
> I would like to add a new parameter {{fs.s3a.metadatastore.getfilestatus.authoritative}} which, when true, keeps the current behavior.  When false, S3AFileSystem will check both S3 and the MetadataStore.
> I'm not sure yet if we want to have this behavior the same for all callers of getFileStatus(), or if we only want to check both S3 and MetadataStore for some internal callers such as open().



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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