[
https://issues.apache.org/jira/browse/HDFS-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996856#comment-13996856
]
Andrew Wang commented on HDFS-6373:
-----------------------------------
That stacktrace is probably just from how symlink resolution works. The client
code catches the UnresolvedLinkException, attempts to resolve it, then retries
with the new path. Maybe we should squish the trace since this is expected
behavior.
> Remove support for extended attributes on symlinks
> --------------------------------------------------
>
> Key: HDFS-6373
> URL: https://issues.apache.org/jira/browse/HDFS-6373
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Andrew Wang
> Assignee: Charles Lamb
>
> Looking in the Linux source code, we see the following:
> http://lxr.linux.no/linux+v3.14.3/fs/xattr.c
> {code}
> 60 /*
> 61 * In the user.* namespace, only regular files and directories
> can have
> 62 * extended attributes. For sticky directories, only the owner and
> 63 * privileged users can write attributes.
> 64 */
> {code}
> We should consider removing {{XAttrFeature}} from {{INodeSymlink}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
