Oozie permissions, task controllers, appTokens

[Jay Vyas <ja...@gmail.com>]

What is the permissions model for appTokens and other job specific files submitted via oozie command line job submissions?  I'm finding that my Linux task controllers are breaking because they don't have permissions to read the appTokens .

Re: Oozie permissions, task controllers, appTokens

[Jay Vyas <ja...@gmail.com>]

Thanks again mona:

1) Not sure what the purpose of the auth.token is - is that required for
running Linux TaskControllers?

2) Is it customary to submit jobs as user "oozie"?

Is there a doc on this somewhere ?  Im not an oozie expert : just want my
user "tom" to be able to submit jobs that the LinuxTaskControllers (running
as "tom") can see - im afraid though that if i run "oozie", it might not
work properly with the yarn LXC .

Anyways, let me know if im missing something.

Re: Oozie permissions, task controllers, appTokens

[Mona Chitnis <ch...@yahoo-inc.com>]

The permissions for the .oozie.auth.token are 600. If you are submitting
Oozie jobs as a different user (task controller) than yourself, consider
authorizing as that user first.

On 2/13/14, 7:10 PM, "Jay Vyas" <ja...@gmail.com> wrote:

>What is the permissions model for appTokens and other job specific files
>submitted via oozie command line job submissions?  I'm finding that my
>Linux task controllers are breaking because they don't have permissions
>to read the appTokens .