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 B1358D3FB for ; Mon, 17 Dec 2012 17:10:07 +0000 (UTC) Received: (qmail 14682 invoked by uid 500); 17 Dec 2012 17:10:02 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 14383 invoked by uid 500); 17 Dec 2012 17:10:02 -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 14375 invoked by uid 99); 17 Dec 2012 17:10:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 17:10:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.210.176 as permitted sender) Received: from [209.85.210.176] (HELO mail-ia0-f176.google.com) (209.85.210.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 17:09:57 +0000 Received: by mail-ia0-f176.google.com with SMTP id y26so5511451iab.35 for ; Mon, 17 Dec 2012 09:09:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=W5C+BawRjYUVofnVle9YE7vz9Hq/lu8I9qOImF9XHsg=; b=QesmEh+6MQsdtcPx8gN6CDKaKVRtbl4PWGWdnd9SwVjSiRIlKkT+qtQsbH00gBR5vr tDmNiuEQ2AV9BJ3OOK7xlwuSFwoNlOhT7wXgvBGAU6WP0BbYWptI8CQsioGJCprjDl06 F0DDOhbh6p5ax2CSsh4/pv+gI7LiC48XNTNnsQTfvEXqDaj4EAhf+AnNroXVe+rXc5Ev +QQYPqd3s1gcQKDZLYU63vZMIquPidKsXEoHzQ9ykZQWFXQQmDOBIQQjNtzxYZbWWj95 YijF7VqX5PL3qQxG3p95P0hv+0GLGVvuYS0k4p+7fFZo44k7nXfHqGZN3wbFnd15u1Sl 7pPA== Received: by 10.50.150.175 with SMTP id uj15mr9674839igb.52.1355764177073; Mon, 17 Dec 2012 09:09:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.6.129 with HTTP; Mon, 17 Dec 2012 09:09:16 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Mon, 17 Dec 2012 22:39:16 +0530 Message-ID: Subject: Re: Is it necessary to run secondary namenode when starting HDFS? To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnncfkcQ24P3mp6U/OdISnsaFSukoT1vYGSrV+T8U7uPfFS+lqtHLvyV0iNBOONxBJ7DjfN X-Virus-Checked: Checked by ClamAV on apache.org The SecondaryNameNode is necessary for automatic maintenance in long-running clusters (read: production), but is not necessary for, nor tied into the basic functions/operations of HDFS. On 1.x, you can remove the script's startup of SNN by removing its host entry from the conf/masters file. On 2.x, you can selectively start the NN and DNs by using the hadoop-daemon.sh script commands. On Mon, Dec 17, 2012 at 10:34 PM, Ivan Ryndin wrote: > Hi all, > > is it necessary to run secondary namenode when starting HDFS? > I am dealing with Hadoop 1.1.1. > Looking at script $HADOOP_HOME/bin/start_dfs.sh > There are next lines in this file: > > # start dfs daemons > # start namenode after datanodes, to minimize time namenode is up w/o data > # note: datanodes will log connection errors until namenode starts > "$bin"/hadoop-daemon.sh --config $HADOOP_CONF_DIR start namenode > $nameStartOpt > "$bin"/hadoop-daemons.sh --config $HADOOP_CONF_DIR start datanode > $dataStartOpt > "$bin"/hadoop-daemons.sh --config $HADOOP_CONF_DIR --hosts masters start > secondarynamenode > > So, will HDFS work if I turn off starting of secondarynamenode ? > > I do ask this because I am playing with Hadoop on two-node cluster only (and > machines in cluster do not have much RAM and disk space), and thus don't > want to run unnecessary processes. > > -- > Best regards, > Ivan P. Ryndin, > -- Harsh J