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 56EA4EFBC for ; Sun, 24 Feb 2013 15:09:58 +0000 (UTC) Received: (qmail 65602 invoked by uid 500); 24 Feb 2013 15:09:53 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 65496 invoked by uid 500); 24 Feb 2013 15:09:52 -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 65483 invoked by uid 99); 24 Feb 2013 15:09:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 24 Feb 2013 15:09:52 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yypvsxf19870706@gmail.com designates 209.85.128.47 as permitted sender) Received: from [209.85.128.47] (HELO mail-qe0-f47.google.com) (209.85.128.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 24 Feb 2013 15:09:45 +0000 Received: by mail-qe0-f47.google.com with SMTP id 2so1116173qea.20 for ; Sun, 24 Feb 2013 07:09:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=H/ZhqpXEQ+sIqEkmBA53ppFwbbaAgtNGSG1acZM+wuE=; b=UBP+goHNBcOSAAMmWbu0e7oqBCR6oER62HOcy3UyZFRBFaFyi01xrx2LIrAHdhCxym RrDwyQLg/Ua/cEM+rCegjf/GIpLCGY5oLv7KwdacS9c69RSm0TXolXMf4VF3hw3ogM2H /6xrbrSf/Uobw4Ud55kAE8uPhO/TaLvWgIakCYzcTeWbcrH5+1ESgQWIg2sWQZa0CapZ 4n2yIA+tUVsKOuS3dDcBeWi9Rqyx3EgEYI4bYkW1Q9fiK60ZXwuMkV8GHr6ntyT9H7bl y9MfdcK/GL6i0BswSsYDJmOIXya/FzttCPA3376uMZppeK5pTnL2oE4q/MJFVq0WOMV0 t+Kw== MIME-Version: 1.0 X-Received: by 10.49.24.135 with SMTP id u7mr7998389qef.4.1361718564751; Sun, 24 Feb 2013 07:09:24 -0800 (PST) Received: by 10.49.82.202 with HTTP; Sun, 24 Feb 2013 07:09:24 -0800 (PST) Date: Sun, 24 Feb 2013 23:09:24 +0800 Message-ID: Subject: One NameNode keeps Rolling Edit Log on HDFS Federation From: YouPeng Yang To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7b6dc3bc560b1104d679cf63 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6dc3bc560b1104d679cf63 Content-Type: text/plain; charset=ISO-8859-1 Hi All I'm testing the HDFS Federation.I have 2 namenodes in my cluster. I find that it is Rolling Edit Log continuously on one namenode,however the other one changes nothing. My question : 1. Is it the right situation. 2. I have thought that the two namenodes shoud keep concurrency. why they get differences. 3. is there any advanced docs about HDFS Federation. thanks. Regards. --047d7b6dc3bc560b1104d679cf63 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All
=A0 =A0
=A0I'm testing the=A0HDFS Federation.I have 2 namenodes in =A0my cluster.<= /span>
=A0I find that it is =A0Rolling Edit Log=A0continuously on one =A0 namenode,however the other one = =A0changes nothing.

=A0My question :
=A01. Is it the right=A0situation.
=A0= 2. I have thought that the two namenodes shoud keep=A0concurrency.
why they get differences.
=A03. is there any adv= anced docs about=A0HDFS Federation.
<= div style>
thanks.

Regards.


=A0
--047d7b6dc3bc560b1104d679cf63--