You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/10/12 05:48:00 UTC
[jira] [Work logged] (HDFS-15625) Namenode trashEmptier should not
init ViewFs on startup
[ https://issues.apache.org/jira/browse/HDFS-15625?focusedWorklogId=499202&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-499202 ]
ASF GitHub Bot logged work on HDFS-15625:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Oct/20 05:47
Start Date: 12/Oct/20 05:47
Worklog Time Spent: 10m
Work Description: umamaheswararao opened a new pull request #2378:
URL: https://github.com/apache/hadoop/pull/2378
https://issues.apache.org/jira/browse/HDFS-15625
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 499202)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org