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 1DC2F1014F for ; Thu, 12 Dec 2013 01:41:37 +0000 (UTC) Received: (qmail 25594 invoked by uid 500); 12 Dec 2013 01:41:32 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 25480 invoked by uid 500); 12 Dec 2013 01:41:32 -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 25473 invoked by uid 99); 12 Dec 2013 01:41:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Dec 2013 01:41:32 +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 kawa.adam@gmail.com designates 209.85.223.179 as permitted sender) Received: from [209.85.223.179] (HELO mail-ie0-f179.google.com) (209.85.223.179) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Dec 2013 01:41:27 +0000 Received: by mail-ie0-f179.google.com with SMTP id x13so12466864ief.38 for ; Wed, 11 Dec 2013 17:41:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UPa3YGYYYT6kdaMUt37tLf70Naegz5dLYJr09SgiAas=; b=NmdHrG7FWrVhyX4PeSF21bMShiQIoEwQ6g71suQL8eVkapDyoSiw4q+MK4+EMBElaq 4bnur+tcHdqEys4PSgMRznWPH5Xn8jZYHZtTV0bncgQu1NPdAoDvDSJYYZ1FW7yw+d// reVZpF6SfAEjd29G01xFEuuF7JhlOmiZaMHmJ+nzADHjgAfKPC33qcyiVE3dXSHlNU/R 2VTtwaCU9vhPykpqL2Iw7ObQIefvpPnbHy3KvhBZCs4t9tZ82DT7re629QaZT6ThZbWQ QtNQne+HlXsUo1njQ0m3O8ZGava4wBhLcfQNf/huvg3V8YKoruIv1tgdw+XJqdOLflRC CvLQ== MIME-Version: 1.0 X-Received: by 10.50.164.196 with SMTP id ys4mr27912493igb.35.1386812466406; Wed, 11 Dec 2013 17:41:06 -0800 (PST) Received: by 10.42.153.136 with HTTP; Wed, 11 Dec 2013 17:41:06 -0800 (PST) In-Reply-To: References: Date: Thu, 12 Dec 2013 02:41:06 +0100 Message-ID: Subject: Re: how to corrupt a replica of a block by manually? From: Adam Kawa To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e01494c326eb65c04ed4c7028 X-Virus-Checked: Checked by ClamAV on apache.org --089e01494c326eb65c04ed4c7028 Content-Type: text/plain; charset=ISO-8859-1 Hmmm.. I guess that you can try to read this file using $ hadoop fs -cat to detect that When reading a file its checksums are calculated and compared to checksums that were calculated during a write operation. If verification fails, NN is notified about the corrupt replica and you will fetch a different replica from another DN to read that file. 2013/12/12 ch huang > hi,maillist: > what is the sample way to corrupt a replica of a block ,i opened a > replica data file ,and delete a line,than use fsck ,nothing corrupt, > should the DN be restarted? > --089e01494c326eb65c04ed4c7028 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hmmm.. I guess that you can try to read this file using=A0=

$ hadoop fs -cat <file-with-corrupt-replica> to detect = that

When reading a file its checksums are calcula= ted and compared to checksums that were calculated during a write operation= . If verification fails, NN is notified about the corrupt replica and you w= ill fetch a different replica from another DN to read that file.


2= 013/12/12 ch huang <justlooks@gmail.com>
hi,maillist:
=A0=A0=A0=A0=A0=A0=A0 what is the sample way to corrupt a replica of a= block ,i opened a replica data file ,and delete a line,than use fsck ,noth= ing corrupt,
=A0should the DN=A0 be restarted?

--089e01494c326eb65c04ed4c7028--