MAPREDUCE-7474. Improve Manifest committer resilience (#6716) #6825
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.
Improve task commit resilience everywhere
and add an option to reduce delete IO requests on
job cleanup (relevant for ABFS and HDFS).
Task Commit Resilience
Task manifest saving is re-attempted on failure; the number of attempts made is configurable with the option:
mapreduce.manifest.committer.manifest.save.attempts
Directory size for deletion
New option
mapreduce.manifest.committer.cleanup.parallel.delete.base.first
This attempts an initial attempt at deleting the base dir, only falling back to parallel deletes if there's a timeout.
This option is disabled by default; Consider enabling it for abfs to reduce IO load. Consult the documentation for more details.
Success file printing
The command to print a JSON _SUCCESS file from this committer and any S3A committer is now something which can be invoked from the mapred command:
mapred successfile
Contributed by Steve Loughran
How was this patch tested?
yetus's work, if happy will validate on abfs.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?