[
https://issues.apache.org/jira/browse/HDFS-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDFS-15625:
----------------------------------
Labels: pull-request-available (was: )
> Namenode trashEmptier should not init ViewFs on startup
> -------------------------------------------------------
>
> Key: HDFS-15625
> URL: https://issues.apache.org/jira/browse/HDFS-15625
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode, viewfs
> Affects Versions: 3.4.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently on NN startup, Namenode starts trash emptier.
> As part of HDFS-15450 we already fixed it by setting fs.hdfs.impl config in
> NN.
> But as part of other JIRAs we seem to be reverted that change.
> If I remember correctly, the issue in HDFS-15450 was about NN can't init
> ViewFsOverloadScheme because, NN always sets it's RPC address in
> fs.defaultFS. So, in HA case, user configured uri would always be a logical
> uri. So, NN could not start it as it can't init because it can't find any
> mount points with that changed fs.defaultFS authority. However that issues
> sorted out as for HDFS we recommend to use ViewHDFS and it will auto set a
> fallback mountpoint if no mount points configured.
> However, we still need that changes needed back as initing
> ViewHDFS/ViewFSOverloadScheme would be costly when it has more mount points.
> Initing this mount based fs in trashEmptier is unnecessary.
> With this JIRA I will just bring back similar functionality back.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
