[
https://issues.apache.org/jira/browse/HADOOP-16458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894104#comment-16894104
]
Steve Loughran commented on HADOOP-16458:
-----------------------------------------
One part of my change is an optimisation for filesystems which don't do
symlinks: we can eliminate the need to do a getFileStatus(path) after a
listFileStatus(path) only returns one entry. This will save some needless HEAD
requests.
I'll do this by making Globber public, add a method to say "no symlinks", and
have the s3a connector use it.
this can also be used by wasb/abfs/gcs/swift and it will also eliminate a
needless HEAD for these too.
> LocatedFileStatusFetcher.getFileStatuses failing intermittently with s3
> -----------------------------------------------------------------------
>
> 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
>
> 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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
