Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
1.2.6, 1.4.3
-
None
-
None
Description
It seems org.apache.hadoop.hbase.snapshot.ExportSnapshot disallows FileSystem instance caching.
When verifySnapshot method is being run it calls often methods like org.apache.hadoop.hbase.util.FSUtils#getRootDir that instantiate FileSystem but never calls org.apache.hadoop.fs.FileSystem#close method. This behaviour allows allocation of unwanted objects potentially causing memory leaks.
Related issue: https://issues.apache.org/jira/browse/HADOOP-15392
Expectation:
- HBase should properly release/close all objects, especially FileSystem instances.
Attachments
Issue Links
- duplicates
-
HBASE-28222 Leak in ExportSnapshot during verifySnapshot on S3A
- Resolved
- is fixed by
-
HBASE-28222 Leak in ExportSnapshot during verifySnapshot on S3A
- Resolved
- is related to
-
HADOOP-15392 S3A Metrics in S3AInstrumentation Cause Memory Leaks in HBase Export
- Resolved
-
HADOOP-17975 Fallback to simple auth does not work for a secondary DistributedFileSystem instance
- Resolved
- relates to
-
HBASE-12819 ExportSnapshot doesn't close FileSystem instances
- Closed