Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF2747AD4 for ; Tue, 29 Nov 2011 16:37:45 +0000 (UTC) Received: (qmail 50843 invoked by uid 500); 29 Nov 2011 16:37:44 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 50804 invoked by uid 500); 29 Nov 2011 16:37:44 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 50796 invoked by uid 99); 29 Nov 2011 16:37:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 16:37:43 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [213.199.154.139] (HELO DB3EHSOBE001.bigfish.com) (213.199.154.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 16:37:35 +0000 Received: from mail105-db3-R.bigfish.com (10.3.81.250) by DB3EHSOBE001.bigfish.com (10.3.84.21) with Microsoft SMTP Server id 14.1.225.22; Tue, 29 Nov 2011 16:36:25 +0000 Received: from mail105-db3 (localhost [127.0.0.1]) by mail105-db3-R.bigfish.com (Postfix) with ESMTP id EDE6C5804AD for ; Tue, 29 Nov 2011 16:36:34 +0000 (UTC) X-SpamScore: -14 X-BigFish: VS-14(zz9371K542M11f6Nzz1202hzz8275dhz2dh87h2a8h668h839h944h) X-Forefront-Antispam-Report: CIP:131.107.125.8;KIP:(null);UIP:(null);IPV:NLI;H:TK5EX14MLTC101.redmond.corp.microsoft.com;RD:none;EFVD:NLI X-FB-SS: 13, X-FB-DOMAIN-IP-MATCH: fail Received: from mail105-db3 (localhost.localdomain [127.0.0.1]) by mail105-db3 (MessageSwitch) id 1322584594482380_13248; Tue, 29 Nov 2011 16:36:34 +0000 (UTC) Received: from DB3EHSMHS005.bigfish.com (unknown [10.3.81.252]) by mail105-db3.bigfish.com (Postfix) with ESMTP id 706E0120048 for ; Tue, 29 Nov 2011 16:36:34 +0000 (UTC) Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (131.107.125.8) by DB3EHSMHS005.bigfish.com (10.3.87.105) with Microsoft SMTP Server (TLS) id 14.1.225.22; Tue, 29 Nov 2011 16:36:23 +0000 Received: from TK5EX14MBXC135.redmond.corp.microsoft.com ([169.254.4.132]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi id 14.02.0247.005; Tue, 29 Nov 2011 08:36:58 -0800 From: Brad Sarsfield To: "common-dev@hadoop.apache.org" Subject: RE: how to write hadoop client to test HDFS with fault injection Thread-Topic: how to write hadoop client to test HDFS with fault injection Thread-Index: AQHMrloe/r1FRI/B+UG/FA1pqOGSgZXEBCHA Date: Tue, 29 Nov 2011 16:36:57 +0000 Message-ID: <1153F8278FF25C49B2024B5CAAD1CAA3692AE0AD@TK5EX14MBXC135.redmond.corp.microsoft.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [157.54.51.21] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: microsoft.com Hi Hao, You may want to setup a full Hadoop 'one box' install and start running the= TestDFSIO, Teragen and Terasort (with a small amount of data) scenarios us= ing the injected jar to run hdfs. That may be the fastest and best way to = get up and running. When it comes to fault injection the valuable issues that you find may be f= ound using the end to end tests versus targeted api calls. It's much more = realistic. It's a much stronger case to get something fixed / fix something= when you can point to the end to end scenario, showing how it can fail. = That's where you find the good ones. You may also want to consider what a data validation oracle would look like= that would allow you to do data validation to catch data corruption issues= . If you do go further and create a scenario that, say generates a non-rand= om / repeatable sequence that reads/writes to HDFS, you could use the fault= injection and the oracle would validate data correctness.=20 You'd get extra bonus points if you packaged things up and contributed your= work to Bigtop so others could benefit long term. ~Brad -----Original Message----- From: Hao Yang [mailto:hao.yang0614@gmail.com]=20 Sent: Monday, November 28, 2011 9:44 PM To: common-dev@hadoop.apache.org Subject: how to write hadoop client to test HDFS with fault injection Hi, all: I am a graduate student, now working on HDFS fault injection course project= . I used FI framework to create aspects, and hdfs-fi.jar was generated. How= can I write Hadoop Client code to test the injection? Thank you. Thank you very much for your time. Best regards Hao Yang