[ 
https://issues.apache.org/jira/browse/FALCON-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372330#comment-14372330
 ] 

Sowmya Ramesh commented on FALCON-933:
--------------------------------------

After https://issues.apache.org/jira/browse/FALCON-753, Staging dir should be 
owned by user and Working dir will still be owned by falcon but readable by 
all. Indeed, we are validating if the staging location owner and permissions. 
If user hits this issue he should change the owner/permission of locations and 
not change the user scheduling the entities.

> misleading error msg on cluster submit failure 
> -----------------------------------------------
>
>                 Key: FALCON-933
>                 URL: https://issues.apache.org/jira/browse/FALCON-933
>             Project: Falcon
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.6
>            Reporter: Samarth Gupta
>            Assignee: Sowmya Ramesh
>             Fix For: 0.6.1
>
>         Attachments: FALCON-933.v0.patch, FALCON-933.v1.patch
>
>
> when cluster submissions fails due to wrong ownership of the "staging" dir , 
> the error msg says "process user"  , where as this is a cluster operation. 
> {code}
> Stacktrace:
> org.apache.falcon.client.FalconCLIException: Bad Request;ua1/Path 
> [/falcon/staging] has owner [hdfs], should be the process user dataqa
>       at 
> org.apache.falcon.client.FalconCLIException.fromReponse(FalconCLIException.java:44)
>       at 
> org.apache.falcon.client.FalconClient.checkIfSuccessful(FalconClient.java:1162)
>       at 
> org.apache.falcon.client.FalconClient.sendEntityRequestWithObject(FalconClient.java:684)
>       at org.apache.falcon.client.FalconClient.submit(FalconClient.java:323)
>       at org.apache.falcon.cli.FalconCLI.entityCommand(FalconCLI.java:361)
>       at org.apache.falcon.cli.FalconCLI.run(FalconCLI.java:182)
>       at org.apache.falcon.cli.FalconCLI.main(FalconCLI.java:132)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to