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 0DA4C1066A for ; Wed, 15 Oct 2014 14:09:38 +0000 (UTC) Received: (qmail 73498 invoked by uid 500); 15 Oct 2014 14:09:33 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 73372 invoked by uid 500); 15 Oct 2014 14:09:33 -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 73361 invoked by uid 99); 15 Oct 2014 14:09:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2014 14:09:33 +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 (athena.apache.org: domain of mahardianto@ugm.ac.id designates 209.85.220.179 as permitted sender) Received: from [209.85.220.179] (HELO mail-vc0-f179.google.com) (209.85.220.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2014 14:09:27 +0000 Received: by mail-vc0-f179.google.com with SMTP id im17so1002671vcb.38 for ; Wed, 15 Oct 2014 07:09:00 -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:date:message-id:subject:from:to :content-type; bh=wb1eh/JLBXDxfdc2cPzwTFTJYqcQdW0uboOZDhsUah0=; b=hTUD8kVVciSq99FbGdMeOIAWI+AAylv0PfpYT31HV4eyMGhhXDG15uxih8ChdZwB0A 3d67tZFB8T5rROg/qrtWuG/FeAuimkbGcmp1xqVSbwrVxbLxEcdZhmOvUPafX+JQYDcp kzyYDr9Icm1BfD0wiUNnakC0O7aQDdRTkk5dfktsjP1lOK3xe2NdrnFzlz4tNR1UJ0F0 W7cIvm9QGbp4sAfNUoxIHaBJt5ImMY3NCdiveCQ91+kOp6d/iPg3twzf7ukJ+Pg06BMu fqVREZjttIhJ4RUn8BvY+sOTB0I/UF7uwYZzLzaHBH8dxj69LOMlCKn88qxiIQtGKKkb +orA== X-Gm-Message-State: ALoCoQmjALQBbRhEgmEfmPd24rxAOeImojumH0BmMTn3Roj1wsU+ZY1kPlOPMtJsMKdE3uxn0PgY MIME-Version: 1.0 X-Received: by 10.52.87.142 with SMTP id ay14mr991988vdb.76.1413382140295; Wed, 15 Oct 2014 07:09:00 -0700 (PDT) Received: by 10.220.240.12 with HTTP; Wed, 15 Oct 2014 07:09:00 -0700 (PDT) Received: by 10.220.240.12 with HTTP; Wed, 15 Oct 2014 07:09:00 -0700 (PDT) Date: Wed, 15 Oct 2014 21:09:00 +0700 Message-ID: Subject: Federation and failover From: Himawan Mahardianto To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=bcaec502d5e6679314050576ac5d X-Virus-Checked: Checked by ClamAV on apache.org --bcaec502d5e6679314050576ac5d Content-Type: text/plain; charset=UTF-8 Does anyone have succeed configured failover namenode with QJM and federation namenode? I was configure 3 namenode (hadoop1, hadoop2, hadoop3) with hadoop1 is active and hadoop2 as a standby for failover, and hadoop3 as other federation namenode with both namenode before (hadoop1 and hadoop2) but when I start the cluster, it won't work with both (federation and failover) feature, just only one feature will be work (failover or federation), what should I do? Thank's before. Note: I used hadoop 2.5.1 --bcaec502d5e6679314050576ac5d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Does anyone have succeed configured failover namenode with Q= JM=C2=A0 and federation namenode? I was configure 3 namenode (hadoop1, hado= op2, hadoop3) with hadoop1 is active and hadoop2 as a standby for failover,= and hadoop3 as other federation namenode with both namenode before (hadoop= 1 and hadoop2) but when I start the cluster, it won't work with both (f= ederation and failover) feature, just only one feature will be work (failov= er or federation), what should I do? Thank's before. Note: I used hadoo= p 2.5.1

--bcaec502d5e6679314050576ac5d--