[SPARK-17666] Ensure that RecordReaders are closed by data source file scans (backport) #15271
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 a branch-2.0 backport of #15245.
What changes were proposed in this pull request?
This patch addresses a potential cause of resource leaks in data source file scans. As reported in SPARK-17666, tasks which do not fully-consume their input may cause file handles / network connections (e.g. S3 connections) to be leaked. Spark's
NewHadoopRDDuses a TaskContext callback to close its record readers, but the new data source file scans will only close record readers once their iterators are fully-consumed.This patch modifies
RecordReaderIteratorandHadoopFileLinesReaderto addclose()methods and modifies all six implementations ofFileFormat.buildReader()to register TaskContext task completion callbacks to guarantee that cleanup is eventually performed.How was this patch tested?
Tested manually for now.