Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 E5DB711DCF for ; Thu, 3 Jul 2014 00:13:07 +0000 (UTC) Received: (qmail 87031 invoked by uid 500); 3 Jul 2014 00:13:04 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 86917 invoked by uid 500); 3 Jul 2014 00:13:03 -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 86907 invoked by uid 99); 3 Jul 2014 00:13:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 00:13:03 +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 varun.uid@gmail.com designates 209.85.214.179 as permitted sender) Received: from [209.85.214.179] (HELO mail-ob0-f179.google.com) (209.85.214.179) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 00:13:01 +0000 Received: by mail-ob0-f179.google.com with SMTP id uz6so13160808obc.24 for ; Wed, 02 Jul 2014 17:12:36 -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=Xu6Ne7ZU37j1GELcJg9fJ9FFE5zDeuz/FAEa8qjIOQ0=; b=IwuqseTEKEPAoPCYKdhQ1o+EwA3EfpVW6J2KpdbEKANMZhiiqRb8wCmgzzQL8mUKS+ iAykZ9KeNvXG+0l5sUpNpHZXuXBvp+xLg58qJfu+Ps2wgYfU4RAlSwSUPFR1H4WdQ30U DD4pNtAzO8gD0OiSyC7NexPyOcUhiK2Wz4YVAMHhsPWblNx8NDif8vxFZU796OrRMLf1 +bC7Dq4ZJ1UyKLjs/2MmXr8wRroDDPctWcJMD8EwK+QqElr9Ztw2fS0QnzcIEIyRGhBv d/l2lQeTyQgLq62dIpWCZRedpKNJ4CoOn8w+WNQfwmepMY4qGNE2hpoVITJH3eb+2Q6x TqXw== MIME-Version: 1.0 X-Received: by 10.60.124.162 with SMTP id mj2mr1229369oeb.22.1404346356192; Wed, 02 Jul 2014 17:12:36 -0700 (PDT) Received: by 10.60.117.198 with HTTP; Wed, 2 Jul 2014 17:12:36 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 Jul 2014 20:12:36 -0400 Message-ID: Subject: Re: A Datanode shutdown question? From: varun kumar To: afsanjar@gmail.com, user Content-Type: multipart/alternative; boundary=047d7b4148feb3dca104fd3eddaf X-Virus-Checked: Checked by ClamAV on apache.org --047d7b4148feb3dca104fd3eddaf Content-Type: text/plain; charset=UTF-8 Generally Datanode sends it heartbeat to namenode for every 3 seconds. If datanode stops sending its heartbeat to name node with in 3 seconds,Namenode thinks it is dead. On Wed, Jul 2, 2014 at 5:03 PM, MrAsanjar . wrote: > If a datanode is shut-downed by calling "hadoop-daemons.sh stop datanode", > how would the namenode gets notified that a datanode is no longer active? > does datanode send a SHUTDOWN_MSG to the namenode? does namenode has to > wait for heartbeat timeout? > -- Regards, Varun Kumar.P --047d7b4148feb3dca104fd3eddaf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Generally Datanode sends it heartbeat to namenode for =C2= =A0every 3 seconds.

If datanode stops sending its = heartbeat to name node with in 3 seconds,Namenode thinks it is dead.
<= /div>


On Wed, Jul 2= , 2014 at 5:03 PM, MrAsanjar . <afsanjar@gmail.com> wrote:<= br>
If a datanode is shut-downed by calling "hadoop-daemo= ns.sh stop datanode", how would the namenode gets notified that a data= node is no longer active? does datanode send a SHUTDOWN_MSG to the namenode= ?=C2=A0 does namenode has to wait for heartbeat timeout?



--
Regards,
Varun Kumar.P=
--047d7b4148feb3dca104fd3eddaf--