Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B469711F5E for ; Fri, 25 Apr 2014 15:43:21 +0000 (UTC) Received: (qmail 2633 invoked by uid 500); 25 Apr 2014 15:43:12 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 2504 invoked by uid 500); 25 Apr 2014 15:43:12 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 2495 invoked by uid 99); 25 Apr 2014 15:43:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2014 15:43:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of samliuhadoop@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qc0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2014 15:43:07 +0000 Received: by mail-qc0-f169.google.com with SMTP id i17so4245846qcy.0 for ; Fri, 25 Apr 2014 08:42:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eZSb1TT8TIu8rE6XfVQfQ54IK8vWfjtoP5QR9jluKTQ=; b=iASwD/hfSnk3Gj9SsGIGeQy/ZTGXh2lynbxBxJuaneMfh36/xMzl9DjcS+ja8aGBvd prJfEbXxjylhVo9sEIHQ622UsSHLUkRK8ubzu8c4thNzyHmFHHghXANLJJEmvAh2kAwG Ou2549OOGS1m0PspjNeLH8oLIeKtGEcypHQtFk3PlpKo5CwQ6hJZXWPqqwIGoWAzKfK9 Csn9nGIkw/ovEcDdKbzXdwZnAoiycf3ySm5LOif6FPpuxaoaAIsaYHA81DOsRFH8vy2V A4chkSHw2l+EmymrXWkZ88GVVieZpeYbinnfzS5SntxBpW8zs9vgjQ06l+HQQwlHziWZ d9zg== MIME-Version: 1.0 X-Received: by 10.224.114.76 with SMTP id d12mr12522002qaq.84.1398440566771; Fri, 25 Apr 2014 08:42:46 -0700 (PDT) Received: by 10.96.56.41 with HTTP; Fri, 25 Apr 2014 08:42:46 -0700 (PDT) In-Reply-To: References: Date: Fri, 25 Apr 2014 23:42:46 +0800 Message-ID: Subject: Re: What codes to chmod 755 to "yarn.nodemanager.log-dirs"? From: sam liu To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7bf0e27a38d48904f7dfd1fb X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf0e27a38d48904f7dfd1fb Content-Type: text/plain; charset=UTF-8 My version is 2.1.0 and the cluster uses DefaultContainerExecutor. Is it possible that DefaultContainerExecutor change the permission of existing nodemanager log-dir to 755? 2014-04-25 0:54 GMT+08:00 Vinod Kumar Vavilapalli : > > Which version of Hadoop are you using? This part of code changed a little, > so asking. > > Also, is this in secure or non-secure mode (DefaultContainerExecutor vs > LinuxContainerExecutor)? Either of those two classes do some more > permission magic and you may be running into those. > > +Vinod > Hortonworks Inc. > http://hortonworks.com/ > > On Thu, Apr 24, 2014 at 9:05 AM, sam liu wrote: > >> Hi Experts, >> >> When the nodemanager log-dirs not exists, I think >> LocalDirsHandlerService#serviceInit will invoke >> DirectoryCollection#createDir to create the log dirs, and chmod 755 to it. >> >> However, when nodemanager log-dirs already exists and with a non 755 >> permission(like 775), I found its permission will still be changed to 755, >> after starting nodemanager. But, I do not think >> DirectoryCollection#createDir did that operation. >> >> What codes to chmod 755 to "yarn.nodemanager.log-dirs"? >> >> > > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. --047d7bf0e27a38d48904f7dfd1fb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
My version is 2.1.0 and the cluster uses DefaultConta= inerExecutor. Is it possible that DefaultContainerExecutor change the permi= ssion of existing nodemanager log-dir to 755?


2014-04-25 0:54 GMT+08:00 Vinod Kumar Va= vilapalli <vinodkv@apache.org>:

Which version of Hadoop are you using? This part of c= ode changed a little, so asking.

Also, is this in secure or no= n-secure mode (DefaultContainerExecutor vs LinuxContainerExecutor)? Either = of those two classes do some more permission magic and you may be running i= nto those.

+Vinod
H= ortonworks Inc.
ht= tp://hortonworks.com/

On Thu, Apr 24, 2014 at 9:05 AM, sam liu <samliuhadoop@gmail.com&= gt; wrote:
Hi Experts,

When the node= manager log-dirs not exists, I think LocalDirsHandlerService#serviceInit wi= ll invoke DirectoryCollection#createDir to create the log dirs, and chmod 7= 55 to it.

However, when nodemanager log-dirs already exists and with a non = 755 permission(like 775), I found its permission will still be changed to 7= 55, after starting nodemanager. But, I do not think DirectoryCollection#cre= ateDir did that operation.

What codes to chmod 755 to "yarn.nodemanager.log-dirs"?=



CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u.

--047d7bf0e27a38d48904f7dfd1fb--