Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AAD8317E56 for ; Tue, 10 Feb 2015 08:36:56 +0000 (UTC) Received: (qmail 12859 invoked by uid 500); 10 Feb 2015 08:36:38 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 12756 invoked by uid 500); 10 Feb 2015 08:36:38 -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 12745 invoked by uid 99); 10 Feb 2015 08:36:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 08:36:37 +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 wget.null@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-wi0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 08:36:09 +0000 Received: by mail-wi0-f172.google.com with SMTP id z2so12474829wiv.5 for ; Tue, 10 Feb 2015 00:34:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:message-id :references:to; bh=ZMld+8VqSk/Yde1swwBroP8T+rVr3TCMfGvPFT/q1RY=; b=R8A8XMJoRuB0ntJ2j6YqMf4ZgrjEzItKih8Gnv5d0+mfg65xDGccAcNmiVqJaH/rRT d7LUUz8ibR+GcXHJFEYh4wAo/jSXjaVOAYU6FeKQky80YuzAu7cN3mNDwv9+SYo0KHJ9 jK55Qz5+yXj93hb72reKU+aiAQO7Xwp/XQxflLfo1/bB10E/khY8ot86pLANm8WXEoXs jBF07dvqZEP6xWYqxq0S7qBuSr5llhy6fUaWYXUjCEPwQ8YJQ6EciRWdy5ekB+Uk++3+ UQ1y9k7QKG1bhAnKGZXBOXu4Cmamcs0a23B1wVyDMD+/vHrESpjv/VqaNJyNcIEAfr5g wdwQ== X-Received: by 10.180.74.199 with SMTP id w7mr4756144wiv.1.1423557278273; Tue, 10 Feb 2015 00:34:38 -0800 (PST) Received: from [172.27.3.151] ([194.127.8.150]) by mx.google.com with ESMTPSA id n3sm19698701wja.36.2015.02.10.00.34.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Feb 2015 00:34:37 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_AFCA3681-19BC-4832-88B0-B4A6227BAE33" Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Stopping ntpd signals SIGTERM, then causes namenode exit From: Alexander Alten-Lorenz X-Priority: 3 In-Reply-To: <75674ac4.d797.14b71242cbb.Coremail.c77_cn@163.com> Date: Tue, 10 Feb 2015 09:34:36 +0100 Message-Id: <6A80D478-1C13-45E9-BEF8-3AC14AAD3CD9@gmail.com> References: <3fe78fb9.5182.14b6c6317a4.Coremail.c77_cn@163.com> <75674ac4.d797.14b71242cbb.Coremail.c77_cn@163.com> To: user@hadoop.apache.org X-Mailer: Apple Mail (2.2070.6) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_AFCA3681-19BC-4832-88B0-B4A6227BAE33 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii The sigterm should be noted in the NN logs, whats happen around 14:00?=20= BR, Alexander=20 > On 10 Feb 2015, at 02:39, David chen wrote: >=20 > Thanks for your reply. > I ever indeed misunderstand how ntpd works, so deployed the shell = script on every node to synchronize time. The reason why the script = contains stopping ntpd command is that the following command 'ntpdate = 192.168.0.1' will fail if miss it. > Now i have understood the difference between ntp and ntpdate, so i = discarded the script, then configured the ntp.conf to synchronize time. > The reason to post the thread is that i wonder why NameNode receive = the SIGTERM signal sent by stopping ntpd command? and why three times = all happened at 14:00:00? --Apple-Mail=_AFCA3681-19BC-4832-88B0-B4A6227BAE33 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
The sigterm should be noted in the NN logs, = whats happen around 14:00? 

BR,
 Alexander 

On 10 Feb 2015, at 02:39, David = chen <c77_cn@163.com> wrote:

Thanks for your reply.
I = ever indeed misunderstand how ntpd works, so deployed the shell = script on every node = to synchronize time. The reason why the script contains stopping ntpd command is that the = following command 'ntpdate 192.168.0.1' will fail if miss = it.
Now i have understood the difference = between ntp and ntpdate, so i discarded the script, then configured the = ntp.conf to synchronize time.
The reason to post = the thread is that i wonder why NameNode receive the SIGTERM signal sent = by stopping ntpd command? and why three times all happened at = 14:00:00?

= --Apple-Mail=_AFCA3681-19BC-4832-88B0-B4A6227BAE33--