Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 61333 invoked from network); 1 Apr 2010 18:45:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 18:45:51 -0000 Received: (qmail 40890 invoked by uid 500); 1 Apr 2010 18:45:51 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 40852 invoked by uid 500); 1 Apr 2010 18:45:51 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 40844 invoked by uid 99); 1 Apr 2010 18:45:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 18:45:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 18:45:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 62815234C4D6 for ; Thu, 1 Apr 2010 18:45:27 +0000 (UTC) Message-ID: <1531288204.640081270147527402.JavaMail.jira@brutus.apache.org> Date: Thu, 1 Apr 2010 18:45:27 +0000 (UTC) From: "Joshua Harlow (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-708) A stress-test tool for HDFS. In-Reply-To: <1458130731.1255576351275.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852501#action_12852501 ] Joshua Harlow commented on HDFS-708: ------------------------------------ Looks good to me as well. Just a couple thoughts/questions. 1. Would it be correct to have a "create" set of jobs job that would ensure before reads/deletes/writes.. that the files exist (instead of generating in a previous job)? That way the data is created on demand, instead of needing to have a separate job that runs beforehand that just does data population (this stage would not affect the overall timing allotted and could be done at the start of the testing)? 2. It would probably be useful to add in a seed number so that the tests can be "mostly" repeated (ie write and deletes can't really be truly repeated since they modify underlying storage)? 3. Might it be useful to add in the future the ability to specify your own distribution "objects" that "generate" operation objects so that the current set of operations can be expanded without core changes, ie a plugin like framework for generating the distribution and for generating the actual set of operations that will occur (allowing for something like a AppendReadDelete operation or similar which will be created distributed according to a square wave as an example)? > A stress-test tool for HDFS. > ---------------------------- > > Key: HDFS-708 > URL: https://issues.apache.org/jira/browse/HDFS-708 > Project: Hadoop HDFS > Issue Type: New Feature > Components: test, tools > Affects Versions: 0.22.0 > Reporter: Konstantin Shvachko > Fix For: 0.22.0 > > Attachments: SLiveTest.pdf > > > It would be good to have a tool for automatic stress testing HDFS, which would provide IO-intensive load on HDFS cluster. > The idea is to start the tool, let it run overnight, and then be able to analyze possible failures. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.