Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 48B9C18D2D for ; Fri, 15 May 2015 04:30:47 +0000 (UTC) Received: (qmail 258 invoked by uid 500); 15 May 2015 04:30:41 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 134 invoked by uid 500); 15 May 2015 04:30:41 -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 123 invoked by uid 99); 15 May 2015 04:30:41 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 May 2015 04:30:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 22459183980 for ; Fri, 15 May 2015 04:30:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.899 X-Spam-Level: ** X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id aYGRvan_Up6x for ; Fri, 15 May 2015 04:30:35 +0000 (UTC) Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id E357D20D6D for ; Fri, 15 May 2015 04:30:34 +0000 (UTC) Received: by iesa3 with SMTP id a3so1736401ies.2 for ; Thu, 14 May 2015 21:30:28 -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=EJ2nb/fbvEiajiWj8/zgQnJJoiMwr7gTeB1tuRSRFn4=; b=d6MC9RCgN3pyM64HphFEoPKKlUYDoyCIqWoShfma7C/+iUgcezU5pfJZeC05IUox7z +KJomAHwrHjiEU7T0shD1rUF9wiTfR1941dofKdE6u9rIJF/utcWdnaNHtY7xbHwlHib Rfpxyk99aKdtp5W7yBBymgXP3eG8XPW9huZdollKO+I0/4AmH+IyXtc1oXanzo2MpQxC zH0zelwuUVMof3Y/ozqGoPjynwmIaHVYDCqr7Uy6kw5vROR3B5TiimxZdF/IhMGoxqRY 3WmMOWghCX3W2yH0uG/I/gNzpxXZ/6wW8qDq21empORcno9n2UZBwjwlmiia2UWiLnVV Xu3Q== MIME-Version: 1.0 X-Received: by 10.50.8.68 with SMTP id p4mr11262367iga.4.1431664228199; Thu, 14 May 2015 21:30:28 -0700 (PDT) Received: by 10.79.93.3 with HTTP; Thu, 14 May 2015 21:30:28 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 May 2015 00:30:28 -0400 Message-ID: Subject: Re: Lifetime of jhist files From: Kevin To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e01184838c2a23e0516174d10 --089e01184838c2a23e0516174d10 Content-Type: text/plain; charset=UTF-8 Thanks, Naga, that worked. I didn't catch that property in the mapred-default.xml. Sorry for such a late response. On Tue, Apr 28, 2015 at 11:01 PM, Naganarasimha G R (Naga) < garlanaganarasimha@huawei.com> wrote: > Hi Kevin, > > Could check the below configuration for the job history server > mapreduce.jobhistory.max-age-ms 604800000 Job history files older than > this many milliseconds will be deleted when the history cleaner runs. > Defaults to 604800000 (1 week). > you could refer other job history configs in* http://hadoop.apache.org/docs/r2.7.0/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml > * > > +Naga > > ------------------------------ > *From:* Kevin [kevin.macksamie@gmail.com] > *Sent:* Wednesday, April 29, 2015 01:11 > *To:* user@hadoop.apache.org > *Subject:* Lifetime of jhist files > > Hi, > > I am running CDH5.1.3 with YARN. The one issue I am having is that the > jhist files are being deleted too quickly. I > set yarn.nodemanager.delete.debug-delay-sec to seven days (in seconds, of > course), but I am noticing that the job historyserver is expiring any jhist > file that is seven days old. I thought > yarn.nodemanager.delete.debug-delay-sec was just to clean up local logs on > the NodeManager; I didn't think it also affected the job history files too. > > Am I right in my assumptions? Is there anyway to extend the lifetime of > the job history files? > > BTW, my history files are stored in > /user/history/done/// > > Any feedback would be great. > > Thanks, > Kevin > --089e01184838c2a23e0516174d10 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, Naga, that worked. I didn't catch that propert= y in the mapred-default.xml. Sorry for such a late response.

On Tue, Apr 28, 2015 at 11= :01 PM, Naganarasimha G R (Naga) <garlanaganarasimha@huawei.co= m> wrote:
Hi Kevin,

Could check the below configuration for the job history server=C2=A0
mapreduce.jobhistory.max-age-ms 604800000 Job history files older than this many milliseconds will be deleted whe= n the history cleaner runs. Defaults to 604800000 (1 week).

you could refer other job history configs in=C2=A0http://hadoop.apache.org/docs/r2.= 7.0/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml=

+Naga


From: Kevin [kevin.macksamie@gmail.com]
Sent: Wednesday, April 29, 2015 01:11
To: user= @hadoop.apache.org
Subject: Lifetime of jhist files

Hi,

I am running CDH5.1.3 with YARN. The one issue I am having is that the= jhist files are being deleted too quickly. I set=C2=A0yarn.nodemanager.del= ete.debug-delay-sec to seven days (in seconds, of course), but I am noticin= g that the job historyserver is expiring any jhist file that is seven days old. I thought yarn.nodemanager.delete.d= ebug-delay-sec was just to clean up local logs on the NodeManager; I didn&#= 39;t think it also affected the job history files too.

Am I right in my assumptions? Is there anyway to extend the lifetime o= f the job history files?

BTW, my history files are stored in /user/history/done/<year>/&l= t;month>/<day>

Any feedback would be great.

Thanks,
Kevin

--089e01184838c2a23e0516174d10--