[HADOOP-17028] ViewFS should initialize target filesystems lazily

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.4.0, 2.10.2, 3.2.3, 3.3.2, 3.1.5
• Component/s: client-mounts, fs, viewfs
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Abhishek Das
• Reporter: Uma Maheswara Rao G
• Created: 05/May/20 06:09
• Updated: 21/Jul/21 01:30
• Resolved: 21/Jul/21 01:30

Description

Currently viewFS initialize all configured target filesystems when viewfs#init itself.

Some target file system initialization involve creating heavy objects and proxy connections. Ex: DistributedFileSystem#initialize will create DFSClient object which will create proxy connections to NN etc.
For example: if ViewFS configured with 10 target fs with hdfs uri and 2 targets with s3a.

If one of the client only work with s3a target, But ViewFS will initialize all targets irrespective of what clients interested to work with. That means, here client will create 10 DFS initializations and 2 s3a initializations. Its unnecessary to have DFS initialization here. So, it will be a good idea to initialize the target fs only when first time usage call come to particular target fs scheme. 

Issue Links

• relates to: HDFS-15289 Allow viewfs mounts with HDFS/HCFS scheme and centralized mount table
• links to: GitHub Pull Request #2260
• links to: GitHub Pull Request #3218