HADOOP-18028. Rebase S3A Prefetch feature branch to trunk #4675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the commit chain of feature-HADOOP-18028-s3a-prefetch rebased to trunk and with a fixup at the end.
I intend to apply this chain to the feature branch with a goal of a squash and merge of the branch into trunk ASAP, with all final work done on trunk
How was this patch tested?
s3 london, params
-Dparallel-tests -DtestsThreadCount=8 -Dscale
all new failures reported
ITestS3SelectLandsat timeout after 10 minutes. surfaces in trunk too.
ITestS3AFileSystemStatistic failure in prefetch feature branch
ITestS3ACannedACLs failure; not in a span.
I don't believe any are related, rather that changing the #of tests triggered latent issues surfacing from different states of the jvm before each suite, or, in the case of the landsat one, some change in the endpoint.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?