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 DAD7317DF7 for ; Mon, 6 Apr 2015 07:29:11 +0000 (UTC) Received: (qmail 94173 invoked by uid 500); 6 Apr 2015 07:29:00 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 94025 invoked by uid 500); 6 Apr 2015 07:29:00 -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 94015 invoked by uid 99); 6 Apr 2015 07:29:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2015 07:29:00 +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 (nike.apache.org: domain of yanghaogn@gmail.com designates 209.85.192.44 as permitted sender) Received: from [209.85.192.44] (HELO mail-qg0-f44.google.com) (209.85.192.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2015 07:28:34 +0000 Received: by qgeb100 with SMTP id b100so6166417qge.3 for ; Mon, 06 Apr 2015 00:27:48 -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=1IY47sCgvCETWk99IAfzucwqF7dU/SOqwN6rZWnJUzo=; b=FywXFSZsIuoxa22o1ZA3Q2y3CFfagrWFcqkAWUA1fZWZMpuDI9jeux6HUgqwsHzD/G lfU04w6c9NOl37iQcmRRA3AtbnP61e5Gb8Qgr85hZjiXiTVsXhk0jVJjaodCRtFdf7AN ZadNiBVyXNnKV0ASuiNbz6TSfx66faHdU3o4XOF+A4fDU9sKYcMcZIkNvHHFTNS556lQ GPAGgUmP76PQ9Jq+EJBcr2W7L52roADH/MykJCK69EMZTl+Ui2qhuu38XoB21KaHLCB8 LncEJ1c7c3v5x+fKmh265F7/m5V7aDpnFdYD3gjBlTPRWWNLLrzorsUnJDanrTdjMCi0 E/bQ== MIME-Version: 1.0 X-Received: by 10.140.107.72 with SMTP id g66mr15183313qgf.70.1428305268126; Mon, 06 Apr 2015 00:27:48 -0700 (PDT) Received: by 10.96.193.137 with HTTP; Mon, 6 Apr 2015 00:27:48 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Apr 2015 15:27:48 +0800 Message-ID: Subject: Re: Question about log files From: =?UTF-8?B?5p2o5rWp?= To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a113a7f2e2338d50513093c21 X-Virus-Checked: Checked by ClamAV on apache.org --001a113a7f2e2338d50513093c21 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I think the log information has lost. the hadoop is not designed for that you deleted these files incorrectly 2015-04-02 11:45 GMT+08:00 =E7=85=9C =E9=9F=A6 : > Hi there, > If log files are deleted without restarting service, it seems that the > logs is to be lost for later operation. For example, on namenode, datanod= e. > Why not log files could be re-created when deleted by mistake or on > purpose during cluster is running? > > Thanks, > Jared > --001a113a7f2e2338d50513093c21 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think the log information has lost.

= =C2=A0the hadoop is not designed for that you deleted these files incorrect= ly

201= 5-04-02 11:45 GMT+08:00 =E7=85=9C =E9=9F=A6 <yu2003w@hotmail.com&g= t;:
Hi there,
If log files are deleted without restart= ing service, it seems that the logs is to be lost for later operation. For = example, on namenode, datanode.
Why not log files could be re-created wh= en deleted by mistake or on purpose during cluster is running?

Thank= s,
Jared

--001a113a7f2e2338d50513093c21--