[
https://issues.apache.org/jira/browse/HADOOP-17028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357581#comment-17357581
]
Konstantin Shvachko edited comment on HADOOP-17028 at 6/4/21, 7:19 PM:
-----------------------------------------------------------------------
I'll re-post here my comment from the linked PR for visibility.
It looks like [[email protected]] deprecated this class later after his
comment. Don't know what prompted the refactoring, but
{{org.apache.hadoop.fs.impl.FunctionsRaisingIOE.FunctionRaisingIOE}}
should be now
{{org.apache.hadoop.util.functional.FunctionRaisingIOE}}
Moving interfaces, which are public by default, from one package to another is
considered an incompatible change, especially since the previous variant had
been released. Besides, it has been committed only to branch-3.3 contributing
to further divergence of the supported branches and making backporting yet
harder.
So [~abhishekd], I prefer to avoid using {{FunctionRaisingIOE}} in this patch
if possible. This will simplify the backport and avoid using unstable APIs.
was (Author: shv):
I'll re-post here mu comment from the linked PR for visibility.
It looks like [[email protected]] deprecated this class later after his
comment. Don't know what prompted the refactoring, but
{{org.apache.hadoop.fs.impl.FunctionsRaisingIOE.FunctionRaisingIOE}}
should be now
{{org.apache.hadoop.util.functional.FunctionRaisingIOE}}
Moving interfaces, which are public by default, from one package to another is
considered an incompatible change, especially since the previous variant had
been released. Besides, it has been committed only to branch-3.3 contributing
to further divergence of the supported branches and making backporting yet
harder.
So [~abhishekd], I prefer to avoid using {{FunctionRaisingIOE}} in this patch
if possible. This will simplify the backport and avoid using unstable APIs.
> ViewFS should initialize target filesystems lazily
> --------------------------------------------------
>
> Key: HADOOP-17028
> URL: https://issues.apache.org/jira/browse/HADOOP-17028
> Project: Hadoop Common
> Issue Type: Bug
> Components: client-mounts, fs, viewfs
> Affects Versions: 3.2.1
> Reporter: Uma Maheswara Rao G
> Assignee: Abhishek Das
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
