You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2020/10/08 14:40:00 UTC
[jira] [Updated] (HADOOP-17293) S3A to always probe S3 in S3A
getFileStatus on non-auth paths
[ https://issues.apache.org/jira/browse/HADOOP-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-17293:
------------------------------------
Summary: S3A to always probe S3 in S3A getFileStatus on non-auth paths (was: refreshing S3Guard records after TTL-triggered-HEAD breaks some workflows)
> S3A to always probe S3 in S3A getFileStatus on non-auth paths
> --------------------------------------------------------------
>
> Key: HADOOP-17293
> URL: https://issues.apache.org/jira/browse/HADOOP-17293
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> an incidental part of HDP-13230 was a fix to innerGetFileStatus, wherein after a HEAD request we would update the DDB record, so resetting it's TTL
> Applications which did remote updates of buckets without going through s3guard are now triggering failures in applications in the cluster when they go to open the file
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org