Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F02E118278 for ; Thu, 16 Jul 2015 20:58:05 +0000 (UTC) Received: (qmail 71705 invoked by uid 500); 16 Jul 2015 20:58:05 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 71578 invoked by uid 500); 16 Jul 2015 20:58:04 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 71340 invoked by uid 99); 16 Jul 2015 20:58:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jul 2015 20:58:04 +0000 Date: Thu, 16 Jul 2015 20:58:04 +0000 (UTC) From: "James Clampffer (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-8790) Add Filesystem level stress tests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 James Clampffer created HDFS-8790: ------------------------------------- Summary: Add Filesystem level stress tests Key: HDFS-8790 URL: https://issues.apache.org/jira/browse/HDFS-8790 Project: Hadoop HDFS Issue Type: Sub-task Components: hdfs-client Reporter: James Clampffer Assignee: James Clampffer I propose adding stress tests on libhdfs(3) compatibility layer was well as the async calls. These can be also used for basic performance metrics and inputs to profiling tools to see improvements over time. I'd like to make these tests into a seperate executable, or set of them, so that they can be used for longer running tests on dedicated clusters that may already exist. Each should provide a simple command line interface for scripted or manual use. Basic tests would be: looped open-read-close sequential scans small random reads All tests will be parameterized for number of threads, read size, and upper and lower offset bounds for a specified file. This will make it much easier to detect and reproduce threading issues and resource leaks as well as provide a simple executable (or set of executables) that can be run with valgrind to gain a high confidence that the code is operating correctly. I'd appreciate suggestions for any other simple stress tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)