[
https://issues.apache.org/jira/browse/HDFS-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004780#comment-17004780
]
Ayush Saxena commented on HDFS-15082:
-------------------------------------
if you have a independent configuration at the router side, If you block at say
255, But the namespace is configured at say 150, your idea or the reason to do
so shall fail, or if different namespace have different values.
Anyway, whoever tends to create the mount point, it is his responsibility to
create the destination too, he should handle?
Moreover, there is something more over here too, say I mount /mnt to at a 255
size dest, if a end user tries to create a directory, /mnt/file, he would get a
exception from the Namenode, that the path length /mnt/file exceeds the
configured value 255 for path. And I don't think we can do much on it, It seems
more of Admin Job to handle these stuff. Not Against, but I don't think this
would add much value and sense, I had couple of discussions internally long
back and all ultimately tend to reach a point where there were no answers.
> RBF: Check each component length of destination path when add/update mount
> entry
> --------------------------------------------------------------------------------
>
> Key: HDFS-15082
> URL: https://issues.apache.org/jira/browse/HDFS-15082
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Reporter: Xiaoqiao He
> Assignee: Xiaoqiao He
> Priority: Major
> Attachments: HDFS-15082.001.patch
>
>
> When add/update mount entry, each component length of destination path could
> exceed filesystem path component length limit, reference to
> `dfs.namenode.fs-limits.max-component-length` of NameNode. So we should check
> each component length of destination path when add/update mount entry at
> Router side.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
