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 5B49610517 for ; Thu, 5 Sep 2013 18:29:15 +0000 (UTC) Received: (qmail 97103 invoked by uid 500); 5 Sep 2013 18:29:10 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 97017 invoked by uid 500); 5 Sep 2013 18:29:10 -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 97010 invoked by uid 99); 5 Sep 2013 18:29:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 18:29:10 +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 (nike.apache.org: domain of harsh@cloudera.com designates 209.85.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 18:29:03 +0000 Received: by mail-ie0-f182.google.com with SMTP id aq17so4529167iec.41 for ; Thu, 05 Sep 2013 11:28:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5KbZL1YMtN6SWBaoenFY4uyvxLkWBMiKRNQ2aKNeDT0=; b=dShmJo0wkxiXN7NqvrPw1m8z9XwgO+/woSMioUHGL2wDJbelT840JmHRsmtfpTPmlN Q64VKBdkMR75KHpbF77CTZPPe7Lob6TukwutkvLoK4s/GPfscPWPtFPNl1+HVSBHRAKc Y5cOOohYsV+HkotCs8PNAOrZS7BRsGVjL1Lac9UJdGDmzoO9mysmfJa2S5uXDRJBsLo1 mwBproJ36/lPYzSJ1yg8C9WFT8tY0og+eXAMS1FARYMfFIFFajBYFH7Yj+yn8f8JFpbR Ppi18uKduQGGpWgxDnIp3MQPOW5fxm20KExybksXHTAb/jZ9PlB0RCjqapoC6wcEcJrH 95Xw== X-Gm-Message-State: ALoCoQmCUyWAMmYejBr43ShBJHijk2oPdZALEpDHrx+2Jg42xL86SHjHbF4TIl9EnNC+6KeB/oLp X-Received: by 10.50.72.33 with SMTP id a1mr6988290igv.58.1378405723006; Thu, 05 Sep 2013 11:28:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.56.105 with HTTP; Thu, 5 Sep 2013 11:28:21 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Thu, 5 Sep 2013 23:58:21 +0530 Message-ID: Subject: Re: SNN not writing data fs.checkpoint.dir location To: "" Cc: smunnavar@yodlee.com Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org These configs need to be present at SNN, not at just the NN. On Thu, Sep 5, 2013 at 11:54 PM, Munna wrote: > Hi Yadav, > > We are using CDH3 and I restarted after changing configuration. > > fs.checkpoint.dir > /data/1/dfs/snn,/nfsmount/dfs/snn > true > > > fs.checkpoint.period > 3600 > The number of seconds between two periodic > checkpoints > > > I have entered these changes in Namenode only. > > > On Thu, Sep 5, 2013 at 11:47 PM, Jitendra Yadav > wrote: >> >> Please share your Hadoop version and hdfs-site.xml conf also I'm >> assuming that you already restarted your cluster after changing >> fs.checkpoint.dir. >> >> Thanks >> On 9/5/13, Munna wrote: >> > Hi, >> > >> > I have configured fs.checkpoint.dir in hdfs-site.xml, but still it was >> > writing in /tmp location. Please give me some solution for checkpointing >> > on >> > respective location. >> > >> > -- >> > *Regards* >> > * >> > * >> > *Munna* >> > > > > > > -- > Regards > > Munna -- Harsh J