Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 209EBDFAC for ; Mon, 17 Dec 2012 12:16:05 +0000 (UTC) Received: (qmail 75831 invoked by uid 500); 17 Dec 2012 12:16:03 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 75742 invoked by uid 500); 17 Dec 2012 12:16:02 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 75709 invoked by uid 99); 17 Dec 2012 12:16:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 12:16:02 +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 (nike.apache.org: local policy) Received: from [209.85.210.169] (HELO mail-ia0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 12:15:54 +0000 Received: by mail-ia0-f169.google.com with SMTP id r4so5675233iaj.14 for ; Mon, 17 Dec 2012 04:15:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=s/BeyPnw2lAMfmoIrT1n8VbcMr25D8eVWGKgvlnm+7o=; b=WZGlq8hI3dToX/NrrKSPOMPBAGotOk+8TRbc+yOgLKHMn5Gr7r66tbUP8VXBs3EalP IOejb4GmhrQ/XH/ZZEEiySl6ew2SxfCJPT3UcG3fkiBAEQGy0//kmrLbYQx4e0MlC3i2 yBy+c+YJclWBJWv0xWCFRg+MH2Pj0E9to6cUNf+wJgl1vCpw+rZ2cCsm2cIIdIidGBqv yBLYENzOiDUoqamVPot5LSpLlRiVgL0pSndTyIiUkNPs1RsnkcjzMjiD3f96VQfT34Br ooP9JDzPw3uNq8Ek71loKkxbkaWOErMipmYVN7DJpYobjKlic/vdCXs4MdjqL/bnRkgm uIvQ== MIME-Version: 1.0 Received: by 10.50.236.104 with SMTP id ut8mr8777447igc.20.1355746532969; Mon, 17 Dec 2012 04:15:32 -0800 (PST) Received: by 10.64.97.36 with HTTP; Mon, 17 Dec 2012 04:15:32 -0800 (PST) In-Reply-To: References: <-7459091258275308652@unknownmsgid> Date: Mon, 17 Dec 2012 07:15:32 -0500 Message-ID: Subject: Re: MR missing lines From: Jean-Marc Spaggiari To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmGBWfCrt/BCzvZpXp2u9e51+peJXMkwNsoksPUMArrhh39okCJAIx7K10+SfBD31IjOqQN X-Virus-Checked: Checked by ClamAV on apache.org The job run the morning, and of course, this time, all the rows got process= ed ;) So I will give it few other tries and will keep you posted if I'm able to reproduce that again. Thanks, JM 2012/12/16, Jean-Marc Spaggiari : > Thanks for the suggestions. > > I already have logs to display all the exepctions and there is > nothing. I can't display the work done, there is to much :( > > I have counters "counting" the rows processed and they match what is > done, minus what is not processed. I have just added few other > counters. One right at the beginning, and one to count what are the > records remaining on the delete list, as suggested. > > I will run the job again tomorrow, see the result and keep you posted. > > JM > > > 2012/12/16, Asaf Mesika : >> Did you check the returned array of the delete method to make sure all >> records sent for delete have been deleted? >> >> Sent from my iPhone >> >> On 16 =D7=91=D7=93=D7=A6=D7=9E 2012, at 14:52, Jean-Marc Spaggiari >> wrote: >> >>> Hi, >>> >>> I have a table where I'm running MR each time is exceding 100 000 rows. >>> >>> When the target is reached, all the feeding process are stopped. >>> >>> Yesterday it reached 123608 rows. So I stopped the feeding process, >>> and ran the MR. >>> >>> For each line, the MR is creating a delete. The delete is placed on a >>> list, and when the list reached 10 elements, it's sent to the table. >>> In the clean method, the list is sent to the table if there is any >>> element in it. >>> >>> So at the en of the MR, I should have an empty table. >>> >>> The table is splitted over 128 regions. And I have 8 region servers. >>> >>> What is disturbing me is that after the MR, I had 38 lines remaining >>> on the table. the MR took 348 minutes to run. So I ran the MR again, >>> which this time took 2 minutes, and now I have 1 row remaining in the >>> table. >>> >>> I looked at the logs (for the 38 lines run) and there is nothing in >>> it. There is some scanner timeout exception for the run of the 100K >>> rows. >>> >>> I'm running HBase 0.94.3. >>> >>> I will hava another 100K rows today, so I will re-run the job. I will >>> increase the timeout to make sure I got no exception, but even when I >>> ran the 38 lines with no exception one was remaining... >>> >>> Any idea why and where I can seach? It's not really an issue for me >>> since I can just re-run the job, but this might be an issue for some >>> others. >>> >>> JM >> >