Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8E8A41088A for ; Tue, 13 Jan 2015 00:19:33 +0000 (UTC) Received: (qmail 47072 invoked by uid 500); 13 Jan 2015 00:19:34 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 46968 invoked by uid 500); 13 Jan 2015 00:19:34 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 46673 invoked by uid 99); 13 Jan 2015 00:19:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2015 00:19:34 +0000 Date: Tue, 13 Jan 2015 00:19:34 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-12782) ITBLL fails for me if generator does anything but 5M per maptask MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274467#comment-14274467 ] Enis Soztutar commented on HBASE-12782: --------------------------------------- yeah, debugging ITBLL has proven to be very hard. What I had done previously was to keep all the files and WAL's and do custom search on top of that. > ITBLL fails for me if generator does anything but 5M per maptask > ---------------------------------------------------------------- > > Key: HBASE-12782 > URL: https://issues.apache.org/jira/browse/HBASE-12782 > Project: HBase > Issue Type: Bug > Components: integration tests > Affects Versions: 1.0.0 > Reporter: stack > Priority: Critical > Fix For: 1.0.0 > > Attachments: 12782.unit.test.and.it.test.txt, 12782.unit.test.writing.txt > > > Anyone else seeing this? If I do an ITBLL with generator doing 5M rows per maptask, all is good -- verify passes. I've been running 5 servers and had one splot per server. So below works: > HADOOP_CLASSPATH="/home/stack/conf_hbase:`/home/stack/hbase/bin/hbase classpath`" ./hadoop/bin/hadoop --config ~/conf_hadoop org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList --monkey serverKilling Generator 5 5000000 g1.tmp > or if I double the map tasks, it works: > HADOOP_CLASSPATH="/home/stack/conf_hbase:`/home/stack/hbase/bin/hbase classpath`" ./hadoop/bin/hadoop --config ~/conf_hadoop org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList --monkey serverKilling Generator 10 5000000 g2.tmp > ...but if I change the 5M to 50M or 25M, Verify fails. > Looking into it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)