[
https://issues.apache.org/jira/browse/HDFS-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996425#comment-13996425
]
Charles Lamb commented on HDFS-6373:
------------------------------------
While investigating this, I noticed this in the TestNameNodeXAttr output. I
suspect it's not intended, but I'll investigate further:
2014-05-13 10:04:33,584 INFO hdfs.StateChange
(FSNamesystem.java:completeFile(3028)) - DIR* completeFile: /symdir2/target is
closed by DFSClient_NONMAPREDUCE_239063403_1
2014-05-13 10:04:33,590 INFO FSNamesystem.audit
(FSNamesystem.java:logAuditMessage(7980)) - allowed=true ugi=cwl
(auth:SIMPLE) ip=/127.0.0.1 cmd=createSymlink src=/symdir1/link
dst=/symdir2/target perm=cwl:supergroup:rwxrwxrwx proto=rpc
2014-05-13 10:04:33,601 INFO FSNamesystem.audit
(FSNamesystem.java:logAuditMessage(7980)) - allowed=true ugi=cwl
(auth:SIMPLE) ip=/127.0.0.1 cmd=setXAttr src=/symdir2/target
dst=null perm=cwl:supergroup:rw-r--r-- proto=rpc
2014-05-13 10:04:33,605 INFO FSNamesystem.audit
(FSNamesystem.java:logAuditMessage(7980)) - allowed=true ugi=cwl
(auth:SIMPLE) ip=/127.0.0.1 cmd=setXAttr src=/symdir2/target
dst=null perm=cwl:supergroup:rw-r--r-- proto=rpc
2014-05-13 10:04:33,608 INFO ipc.Server (Server.java:run(2120)) - IPC Server
handler 9 on 38622, call
org.apache.hadoop.hdfs.protocol.ClientProtocol.getXAttrs from 127.0.0.1:41722
Call#18 Retry#0
org.apache.hadoop.hdfs.protocol.UnresolvedPathException: /symdir2/target
at
org.apache.hadoop.hdfs.server.namenode.INodesInPath.resolve(INodesInPath.java:203)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.getLastINodeInPath(FSDirectory.java:3135)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.getXAttrs(FSDirectory.java:2952)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getXAttrs(FSNamesystem.java:7858)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getXAttrs(NameNodeRpcServer.java:1396)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getXAttrs(ClientNamenodeProtocolServerSideTranslatorPB.java:1294)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:605)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:932)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2099)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2095)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1608)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2093)
> 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)
