Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # user >> Yarn log directory perms


Copy link to this message
-
Re: Yarn log directory perms
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 <[EMAIL PROTECTED]>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
>> <[EMAIL PROTECTED]> 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
>>
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB