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/11/30 10:34:00 UTC

[jira] [Updated] (HADOOP-16458) LocatedFileStatusFetcher scans failing intermittently against S3 store

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

Steve Loughran updated HADOOP-16458:
------------------------------------
    Parent Issue: HADOOP-17400  (was: HADOOP-15620)

> LocatedFileStatusFetcher scans failing intermittently against S3 store
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-16458
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16458
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>         Environment: S3 + S3Guard
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Intermittent failure of LocatedFileStatusFetcher.getFileStatuses(), which is using globStatus to find files.
> I'd say "turn s3guard on" except this appears to be the case, and the dataset being read is
> over 1h old.
> Which means it is harder than I'd like to blame S3 for what would sound like an inconsistency
> We're hampered by the number of debug level statements in the globber code being approximately none; there's no debugging to turn on. All we know is that globFiles returns null without any explanation.



--
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