[
https://issues.apache.org/jira/browse/TEZ-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511434#comment-14511434
]
TezQA commented on TEZ-2364:
----------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12727953/TEZ-2364.1.txt
against master revision bbbebb8.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/531//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/531//console
This message is automatically generated.
> 'joindatagen' AM picks wrong staging dir
> ----------------------------------------
>
> Key: TEZ-2364
> URL: https://issues.apache.org/jira/browse/TEZ-2364
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Yesha Vora
> Assignee: Siddharth Seth
> Fix For: 0.7.0
>
> Attachments: TEZ-2364.1.txt
>
>
> joindatagen application is run as hrt_qa user. and tez.staging-dir is set as
> {noformat}'/tmp/${user.name}/staging'{noformat}
> Here, AM tries to access "/tmp/yarn/staging" dir instead
> "/tmp/hrt_qa/staging".
> {code}
> 2015-04-23 21:09:13,032 INFO [main] app.DAGAppMaster: Comparing client
> version with AM version, clientVersion=0.7.0.2.3.0.0-1716,
> AMVersion=0.7.0.2.3.0.0-1716
> 2015-04-23 21:09:14,653 INFO [main] service.AbstractService: Service
> org.apache.tez.dag.app.DAGAppMaster failed in state INITED; cause:
> org.apache.tez.dag.api.TezUncheckedException:
> org.apache.hadoop.security.AccessControlException: Permission denied:
> user=hrt_qa, access=EXECUTE, inode="/tmp/yarn/staging":yarn:hdfs:drwx------
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkTraverse(FSPermissionChecker.java:259)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:205)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1698)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirStatAndListingOp.getFileInfo(FSDirStatAndListingOp.java:108)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3849)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1005)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:843)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2049)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2045)
> 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:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2043)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
