[jira] [Resolved] (HADOOP-17293) S3A to always probe S3 in S3A getFileStatus on non-auth paths

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (HADOOP-17293) S3A to always probe S3 in S3A getFileStatus on non-auth paths

Nicholas DiPiazza (Jira)

     [ https://issues.apache.org/jira/browse/HADOOP-17293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-17293.
-------------------------------------
    Fix Version/s: 3.3.1
       Resolution: Fixed

>  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
>             Fix For: 3.3.1
>
>          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: [hidden email]
For additional commands, e-mail: [hidden email]