You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hadoop.apache.org by Prashant Kommireddi <pr...@gmail.com> on 2013/09/13 23:07:27 UTC
Yarn log directory perms
Hey guys,
It looks like the default perms for app/container dirs is set to 710 and is
not configurable. From DefaultContainerExecutor
/** Permissions for user log dir.
* $logdir/$user/$appId */
private static final short LOGDIR_PERM = (short)0710;
Any reasons for not having this be a configurable property?
Thanks,
Prashant
Re: Yarn log directory perms
Posted by Shahab Yunus <sh...@gmail.com>.
Just a thought, I don't know how much it makes sense, why not run that
program as the user who is allowed to read that directory and you can then
allow that user to write to whichever directory you want to forward your
logs?
Regards,
Shahab
On Sat, Sep 14, 2013 at 6:47 PM, Prashant Kommireddi <pr...@gmail.com>wrote:
> Thanks Harsh. It makes sense that 710 is the default. But admins should be
> able to configure it differently if required? In our case , we have a
> separate process (running as a different user) that forwards logs to
> another system. We are unable to do so now due to the default perms.
>
> On Friday, September 13, 2013, Harsh J wrote:
>
>> This is true for MRv1 too, and is done so for security reasons.
>>
>> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
>> <pr...@gmail.com> wrote:
>> > Hey guys,
>> >
>> > It looks like the default perms for app/container dirs is set to 710
>> and is
>> > not configurable. From DefaultContainerExecutor
>> >
>> > /** Permissions for user log dir.
>> > * $logdir/$user/$appId */
>> > private static final short LOGDIR_PERM = (short)0710;
>> >
>> >
>> > Any reasons for not having this be a configurable property?
>> >
>> > Thanks,
>> > Prashant
>>
>>
>>
>> --
>> Harsh J
>>
>
Re: Yarn log directory perms
Posted by Shahab Yunus <sh...@gmail.com>.
Just a thought, I don't know how much it makes sense, why not run that
program as the user who is allowed to read that directory and you can then
allow that user to write to whichever directory you want to forward your
logs?
Regards,
Shahab
On Sat, Sep 14, 2013 at 6:47 PM, Prashant Kommireddi <pr...@gmail.com>wrote:
> Thanks Harsh. It makes sense that 710 is the default. But admins should be
> able to configure it differently if required? In our case , we have a
> separate process (running as a different user) that forwards logs to
> another system. We are unable to do so now due to the default perms.
>
> On Friday, September 13, 2013, Harsh J wrote:
>
>> This is true for MRv1 too, and is done so for security reasons.
>>
>> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
>> <pr...@gmail.com> wrote:
>> > Hey guys,
>> >
>> > It looks like the default perms for app/container dirs is set to 710
>> and is
>> > not configurable. From DefaultContainerExecutor
>> >
>> > /** Permissions for user log dir.
>> > * $logdir/$user/$appId */
>> > private static final short LOGDIR_PERM = (short)0710;
>> >
>> >
>> > Any reasons for not having this be a configurable property?
>> >
>> > Thanks,
>> > Prashant
>>
>>
>>
>> --
>> Harsh J
>>
>
Re: Yarn log directory perms
Posted by Shahab Yunus <sh...@gmail.com>.
Just a thought, I don't know how much it makes sense, why not run that
program as the user who is allowed to read that directory and you can then
allow that user to write to whichever directory you want to forward your
logs?
Regards,
Shahab
On Sat, Sep 14, 2013 at 6:47 PM, Prashant Kommireddi <pr...@gmail.com>wrote:
> Thanks Harsh. It makes sense that 710 is the default. But admins should be
> able to configure it differently if required? In our case , we have a
> separate process (running as a different user) that forwards logs to
> another system. We are unable to do so now due to the default perms.
>
> On Friday, September 13, 2013, Harsh J wrote:
>
>> This is true for MRv1 too, and is done so for security reasons.
>>
>> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
>> <pr...@gmail.com> wrote:
>> > Hey guys,
>> >
>> > It looks like the default perms for app/container dirs is set to 710
>> and is
>> > not configurable. From DefaultContainerExecutor
>> >
>> > /** Permissions for user log dir.
>> > * $logdir/$user/$appId */
>> > private static final short LOGDIR_PERM = (short)0710;
>> >
>> >
>> > Any reasons for not having this be a configurable property?
>> >
>> > Thanks,
>> > Prashant
>>
>>
>>
>> --
>> Harsh J
>>
>
Re: Yarn log directory perms
Posted by Shahab Yunus <sh...@gmail.com>.
Just a thought, I don't know how much it makes sense, why not run that
program as the user who is allowed to read that directory and you can then
allow that user to write to whichever directory you want to forward your
logs?
Regards,
Shahab
On Sat, Sep 14, 2013 at 6:47 PM, Prashant Kommireddi <pr...@gmail.com>wrote:
> Thanks Harsh. It makes sense that 710 is the default. But admins should be
> able to configure it differently if required? In our case , we have a
> separate process (running as a different user) that forwards logs to
> another system. We are unable to do so now due to the default perms.
>
> On Friday, September 13, 2013, Harsh J wrote:
>
>> This is true for MRv1 too, and is done so for security reasons.
>>
>> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
>> <pr...@gmail.com> wrote:
>> > Hey guys,
>> >
>> > It looks like the default perms for app/container dirs is set to 710
>> and is
>> > not configurable. From DefaultContainerExecutor
>> >
>> > /** Permissions for user log dir.
>> > * $logdir/$user/$appId */
>> > private static final short LOGDIR_PERM = (short)0710;
>> >
>> >
>> > Any reasons for not having this be a configurable property?
>> >
>> > Thanks,
>> > Prashant
>>
>>
>>
>> --
>> Harsh J
>>
>
Re: Yarn log directory perms
Posted by Prashant Kommireddi <pr...@gmail.com>.
Thanks Harsh. It makes sense that 710 is the default. But admins should be
able to configure it differently if required? In our case , we have a
separate process (running as a different user) that forwards logs to
another system. We are unable to do so now due to the default perms.
On Friday, September 13, 2013, Harsh J wrote:
> This is true for MRv1 too, and is done so for security reasons.
>
> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
> <prash1784@gmail.com <javascript:;>> wrote:
> > Hey guys,
> >
> > It looks like the default perms for app/container dirs is set to 710 and
> is
> > not configurable. From DefaultContainerExecutor
> >
> > /** Permissions for user log dir.
> > * $logdir/$user/$appId */
> > private static final short LOGDIR_PERM = (short)0710;
> >
> >
> > Any reasons for not having this be a configurable property?
> >
> > Thanks,
> > Prashant
>
>
>
> --
> Harsh J
>
Re: Yarn log directory perms
Posted by Prashant Kommireddi <pr...@gmail.com>.
Thanks Harsh. It makes sense that 710 is the default. But admins should be
able to configure it differently if required? In our case , we have a
separate process (running as a different user) that forwards logs to
another system. We are unable to do so now due to the default perms.
On Friday, September 13, 2013, Harsh J wrote:
> This is true for MRv1 too, and is done so for security reasons.
>
> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
> <prash1784@gmail.com <javascript:;>> wrote:
> > Hey guys,
> >
> > It looks like the default perms for app/container dirs is set to 710 and
> is
> > not configurable. From DefaultContainerExecutor
> >
> > /** Permissions for user log dir.
> > * $logdir/$user/$appId */
> > private static final short LOGDIR_PERM = (short)0710;
> >
> >
> > Any reasons for not having this be a configurable property?
> >
> > Thanks,
> > Prashant
>
>
>
> --
> Harsh J
>
Re: Yarn log directory perms
Posted by Prashant Kommireddi <pr...@gmail.com>.
Thanks Harsh. It makes sense that 710 is the default. But admins should be
able to configure it differently if required? In our case , we have a
separate process (running as a different user) that forwards logs to
another system. We are unable to do so now due to the default perms.
On Friday, September 13, 2013, Harsh J wrote:
> This is true for MRv1 too, and is done so for security reasons.
>
> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
> <prash1784@gmail.com <javascript:;>> wrote:
> > Hey guys,
> >
> > It looks like the default perms for app/container dirs is set to 710 and
> is
> > not configurable. From DefaultContainerExecutor
> >
> > /** Permissions for user log dir.
> > * $logdir/$user/$appId */
> > private static final short LOGDIR_PERM = (short)0710;
> >
> >
> > Any reasons for not having this be a configurable property?
> >
> > Thanks,
> > Prashant
>
>
>
> --
> Harsh J
>
Re: Yarn log directory perms
Posted by Prashant Kommireddi <pr...@gmail.com>.
Thanks Harsh. It makes sense that 710 is the default. But admins should be
able to configure it differently if required? In our case , we have a
separate process (running as a different user) that forwards logs to
another system. We are unable to do so now due to the default perms.
On Friday, September 13, 2013, Harsh J wrote:
> This is true for MRv1 too, and is done so for security reasons.
>
> On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
> <prash1784@gmail.com <javascript:;>> wrote:
> > Hey guys,
> >
> > It looks like the default perms for app/container dirs is set to 710 and
> is
> > not configurable. From DefaultContainerExecutor
> >
> > /** Permissions for user log dir.
> > * $logdir/$user/$appId */
> > private static final short LOGDIR_PERM = (short)0710;
> >
> >
> > Any reasons for not having this be a configurable property?
> >
> > Thanks,
> > Prashant
>
>
>
> --
> Harsh J
>
Re: Yarn log directory perms
Posted by Harsh J <ha...@cloudera.com>.
This is true for MRv1 too, and is done so for security reasons.
On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
<pr...@gmail.com> wrote:
> Hey guys,
>
> It looks like the default perms for app/container dirs is set to 710 and is
> not configurable. From DefaultContainerExecutor
>
> /** Permissions for user log dir.
> * $logdir/$user/$appId */
> private static final short LOGDIR_PERM = (short)0710;
>
>
> Any reasons for not having this be a configurable property?
>
> Thanks,
> Prashant
--
Harsh J
Re: Yarn log directory perms
Posted by Harsh J <ha...@cloudera.com>.
This is true for MRv1 too, and is done so for security reasons.
On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
<pr...@gmail.com> wrote:
> Hey guys,
>
> It looks like the default perms for app/container dirs is set to 710 and is
> not configurable. From DefaultContainerExecutor
>
> /** Permissions for user log dir.
> * $logdir/$user/$appId */
> private static final short LOGDIR_PERM = (short)0710;
>
>
> Any reasons for not having this be a configurable property?
>
> Thanks,
> Prashant
--
Harsh J
Re: Yarn log directory perms
Posted by Harsh J <ha...@cloudera.com>.
This is true for MRv1 too, and is done so for security reasons.
On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
<pr...@gmail.com> wrote:
> Hey guys,
>
> It looks like the default perms for app/container dirs is set to 710 and is
> not configurable. From DefaultContainerExecutor
>
> /** Permissions for user log dir.
> * $logdir/$user/$appId */
> private static final short LOGDIR_PERM = (short)0710;
>
>
> Any reasons for not having this be a configurable property?
>
> Thanks,
> Prashant
--
Harsh J
Re: Yarn log directory perms
Posted by Harsh J <ha...@cloudera.com>.
This is true for MRv1 too, and is done so for security reasons.
On Sat, Sep 14, 2013 at 2:37 AM, Prashant Kommireddi
<pr...@gmail.com> wrote:
> Hey guys,
>
> It looks like the default perms for app/container dirs is set to 710 and is
> not configurable. From DefaultContainerExecutor
>
> /** Permissions for user log dir.
> * $logdir/$user/$appId */
> private static final short LOGDIR_PERM = (short)0710;
>
>
> Any reasons for not having this be a configurable property?
>
> Thanks,
> Prashant
--
Harsh J