[
https://issues.apache.org/jira/browse/HDFS-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409311#comment-17409311
]
Ayush Saxena commented on HDFS-16196:
-------------------------------------
What do you mean by entire path? The path with respect to Router, before mount
point resolution? If so, we can not pass that to Namenode, the namenode is
least bothered with the client logic, Someone coming through ViewFs would also
expect similar behaviour. Logs aren't for the end-client, If for debuging, the
Admin would be smart enough and aware of the mount points to decode the path.
> Namesystem#completeFile method will log incorrect path information when
> router to access
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-16196
> URL: https://issues.apache.org/jira/browse/HDFS-16196
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: lei w
> Priority: Minor
>
> Router not send entire path information to namenode because
> ClientProtocol#complete method`s parameter with fileId. Then NameNode will
> log incorrect path information. This is very confusing, should we let the
> router pass the path information or modify the log path on namenode?
> completeFile log as fllow:
> StateChange: DIR* completeFile: / is closed by DFSClient_NONMAPREDUC_*****
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
