Description
We seen this with S3A but it is likely to apply to the other file systems too:
If the file system raises an exception during initialize() then it is not close()'d. Any resources threads etc created during initialisation may be leaked.
I'm going to fix S3A to clean up internally, but the FileSystem get() and newInstance() methods should also catch and close if an IOE or RTE is raised.
Attachments
Issue Links
- is depended upon by
-
HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
- Resolved
- links to