Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 7AB9210AC1 for ; Fri, 28 Nov 2014 09:33:05 +0000 (UTC) Received: (qmail 87270 invoked by uid 500); 28 Nov 2014 09:33:00 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 87151 invoked by uid 500); 28 Nov 2014 09:33:00 -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 87117 invoked by uid 99); 28 Nov 2014 09:33:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2014 09:33:00 +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 louis.hust.ml@gmail.com designates 209.85.192.180 as permitted sender) Received: from [209.85.192.180] (HELO mail-pd0-f180.google.com) (209.85.192.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2014 09:32:55 +0000 Received: by mail-pd0-f180.google.com with SMTP id p10so6409969pdj.39 for ; Fri, 28 Nov 2014 01:31:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:message-id :references:to; bh=8OEIEQxtsr8cWqbvVCBEGs/sr6a8mJTZ4MvYQU5U7rI=; b=QxyDwWOiKI8Av/uiihDEv2S4dVXZ0iHjiWtB9FG9aaeqbGoxCRhBBKsi1mRb56HAvb FUb4WGpQfSgQTKnliM+VIRjDr+Wlmadu1oKH9AVNER2XJGihLou5ficE3APh3PX4reDa 8DQFAPgkMvQKhHHdrpnAqTAF4U4B8SuOmDgkjvIJzY9Ob4vL2XxBUNjueW431RRUlmjY AWDCbUsYG0SVzsa5ymzxTYKNb7XZK1L9eh7zwBdNB4XyRW2UUyQhLLlrS8AAwMy2wG8r yLEqts/rU4SOruYs5779PdFMSTCJM36/xuLDyakThzsE06kIrQaE95Ig2S8/axcHWniH VqfA== X-Received: by 10.67.14.71 with SMTP id fe7mr71198803pad.27.1417167110398; Fri, 28 Nov 2014 01:31:50 -0800 (PST) Received: from [192.168.1.102] ([60.208.162.21]) by mx.google.com with ESMTPSA id il5sm9305553pbb.56.2014.11.28.01.31.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Nov 2014 01:31:49 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_D2A03AE4-2DBC-4B9B-A07A-9064B0BCD9E1" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: =?utf-8?Q?Re=3A_after__QJM_failover=EF=BC=8Chbase__can_not__writ?= =?utf-8?Q?e?= From: mail list X-Priority: 3 In-Reply-To: Date: Fri, 28 Nov 2014 17:31:42 +0800 Message-Id: <20A2E7E9-39FB-4337-A673-4789D263E3FF@gmail.com> References: To: user@hadoop.apache.org X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_D2A03AE4-2DBC-4B9B-A07A-9064B0BCD9E1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, please attach your log when the problem happened!! On Nov 28, 2014, at 14:32, =E8=81=AA=E8=81=AA <175998806@qq.com> wrote: > hi=EF=BC=8Cthere: > I encount a problem=EF=BC=8Cit let me upset. >=20 > I use version of hadoop is hadoop-2.3.0-cdh5.1.0=EF=BC=8Cnamenode HA = use the Quorum Journal Manager (QJM) feature =EF=BC=8Cdfs.ha.fencing.meth= ods option is following=EF=BC=9A > > dfs.ha.fencing.methods > sshfence > shell(q_hadoop_fence.sh $target_host $target_port) > > >=20 > or >=20 > > dfs.ha.fencing.methods > sshfence > shell(/bin/true) > > >=20 > I use iptables to simulate machine of active namenode crash=E3=80=82A= fter automatic failover completed=EF=BC=8Chdfs can the normal = write=EF=BC=8Cfor example ./bin/hdfs dfs -put a.txt /tmp,but hbase = still can not write. > After a very long time=EF=BC=8Chbase can write,but I can not statistic = How long did it take. > I want to ask=EF=BC=9A > 1=E3=80=81Why hdfs Complete failover=EF=BC=8Chbase can not write=EF=BC=9F= > 2=E3=80=81After hdfs Complete failover=EF=BC=8Chow long hbase can = write=EF=BC=9F > Looking forward for your responses! --Apple-Mail=_D2A03AE4-2DBC-4B9B-A07A-9064B0BCD9E1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

please attach your log when = the problem happened!!

On Nov 28, 2014, at = 14:32, =E8=81=AA=E8=81=AA <175998806@qq.com> = wrote:

hi=EF=BC=8Cthere:
I encount a problem=EF=BC=8Cit let me upset.

I use version of hadoop is hadoop-2.3.0-cdh5.1.0=EF=BC=8Cnamenode = HA use the Quorum Journal Manager (QJM) = feature =EF=BC=8Cdfs.ha.fencing.methods option is = following=EF=BC=9A
<property>
= <name>dfs.ha.fencing.methods</name>
<value>sshfence
= shell(q_hadoop_fence.sh $target_host $target_port)
</value>
</property>

or

<property>
= <name>dfs.ha.fencing.methods</name>
<value>sshfence
= shell(/bin/true)
= </value>
</property>

I use iptables to simulate = machine of active namenode crash=E3=80=82After = automatic failover completed=EF=BC=8Chdfs can the = normal write=EF=BC=8Cfor example ./bin/hdfs dfs -put a.txt /tmp,but = hbase still can not write.
After a = very long time=EF=BC=8Chbase can write,but I can not = statistic How long did it take.
I want to ask=EF=BC=9A
<= div style=3D"display: block; font-size: 14px; font-family: Verdana; = font-weight: normal; font-style: normal; background-color: rgba(0, 0, 0, = 0);">1=E3=80=81Why hdfs Complete failover=EF=BC=8Chbase can not = write=EF=BC=9F

2=E3=80=81After hdfs Complete = failover=EF=BC=8Chow long hbase can write=EF=BC=9F

Looking forward for your responses!=E2=80=8D

=E2=80=8D

= --Apple-Mail=_D2A03AE4-2DBC-4B9B-A07A-9064B0BCD9E1--