-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-18948. S3A. Add option fs.s3a.directory.operations.purge.uploads to purge on rename/delete #6218
HADOOP-18948. S3A. Add option fs.s3a.directory.operations.purge.uploads to purge on rename/delete #6218
Conversation
💔 -1 overall
This message was automatically generated. |
066da37
to
ba65cf7
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
ba65cf7
to
01c33bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, small nit.
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/Statistic.java
Outdated
Show resolved
Hide resolved
…ds to purge on rename/delete Delete and rename get to optionally pending uploads in a separate thread. * Adds test ITestUploadPurgeOnDirectoryOperations to validate outcome and cost * Fix up instrumentation to distinguish api calls from store operations * Fix up audit spans to ensure abort calls are in spans. * Doc in third_party docs with all existing options added. * list multiparts ensured the path to delete must always end in a / That's needed to avoid deleting uploads in adjacent directories. * fix tests failing by that / append & which were asserting on the file path rather than the parent dir. Change-Id: I3e75c8da9e93be05ab7cb3703e5336026dec1ace
01c33bb
to
d227ce5
Compare
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
…ds to purge on rename/delete (apache#6218) S3A directory delete and rename will optionally abort all pending multipart uploads in their under their to-be-deleted paths when. fs.s3a.directory.operations.purge.upload is true It is off by default. The filesystems hasPathCapability("fs.s3a.directory.operations.purge.upload") probe will return true when this feature is enabled. Multipart uploads may accrue from interrupted data writes, uncommitted staging/magic committer jobs and other operations/applications. On AWS S3 lifecycle rules are the recommended way to clean these; this change improves support for stores which lack these rules. Contributed by Steve Loughran
…ds to purge on rename/delete (apache#6218) S3A directory delete and rename will optionally abort all pending multipart uploads in their under their to-be-deleted paths when. fs.s3a.directory.operations.purge.upload is true It is off by default. The filesystems hasPathCapability("fs.s3a.directory.operations.purge.upload") probe will return true when this feature is enabled. Multipart uploads may accrue from interrupted data writes, uncommitted staging/magic committer jobs and other operations/applications. On AWS S3 lifecycle rules are the recommended way to clean these; this change improves support for stores which lack these rules. Contributed by Steve Loughran
…ds to purge on rename/delete (apache#6218) S3A directory delete and rename will optionally abort all pending multipart uploads in their under their to-be-deleted paths when. fs.s3a.directory.operations.purge.upload is true It is off by default. The filesystems hasPathCapability("fs.s3a.directory.operations.purge.upload") probe will return true when this feature is enabled. Multipart uploads may accrue from interrupted data writes, uncommitted staging/magic committer jobs and other operations/applications. On AWS S3 lifecycle rules are the recommended way to clean these; this change improves support for stores which lack these rules. Contributed by Steve Loughran
…ds to purge on rename/delete (apache#6218) S3A directory delete and rename will optionally abort all pending multipart uploads in their under their to-be-deleted paths when. fs.s3a.directory.operations.purge.upload is true It is off by default. The filesystems hasPathCapability("fs.s3a.directory.operations.purge.upload") probe will return true when this feature is enabled. Multipart uploads may accrue from interrupted data writes, uncommitted staging/magic committer jobs and other operations/applications. On AWS S3 lifecycle rules are the recommended way to clean these; this change improves support for stores which lack these rules. Contributed by Steve Loughran
Delete and rename get to optionally purge in-flight uploads.
no test; just a fix for those itests which failed once the production code adds the rule that the path to delete must always end in a / That's needed to avoid deleting uploads in adjacent directories.
How was this patch tested?
s3 london; fixed some s3guard tests which were trying to purge uploads on a path, not a dir.
I do plan to write a new test
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?