Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 48927 invoked from network); 2 Dec 2010 10:17:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Dec 2010 10:17:59 -0000 Received: (qmail 14694 invoked by uid 500); 2 Dec 2010 10:17:58 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 14579 invoked by uid 500); 2 Dec 2010 10:17:57 -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 14563 invoked by uid 99); 2 Dec 2010 10:17:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Dec 2010 10:17:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lars.george@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-ew0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Dec 2010 10:17:50 +0000 Received: by ewy27 with SMTP id 27so4463648ewy.14 for ; Thu, 02 Dec 2010 02:17:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=wApJktRoygBZBflylaTc7ABNkC7sH14esANYB/oLk6Q=; b=RIezaOmIXfHB9qXz81Dyvwz1YAwhJe+IUvCDc5jTxJSaIuSLbTxmFvZdcq7hs52eqs /cozWL8BNv6r6quzMHGUpduagZrA4Ekc41IrxajzuulKVYCVzEG6AxEsLoBXlg2ss9Dx gez8THsM+VJcq/LxhcmXncCEmCzwcUzK39oeo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=gI+u6eNe15O9eZUuCOAkr7E/98bh23E02y4+jYXtL96k63pwDIIVegMEwgFQSHuGYF l16aiLBIwSR0FZ0gTNeAeMrL7uPI3V0Wx7RN+kRn/gVNNCgWp+IfY4j1uHWUEvofKNM1 9FfDeMIMfa/UXbTvDjwqcpKTyYf4aRQMu9nS8= MIME-Version: 1.0 Received: by 10.213.12.197 with SMTP id y5mr2055310eby.83.1291285046709; Thu, 02 Dec 2010 02:17:26 -0800 (PST) Received: by 10.213.35.140 with HTTP; Thu, 2 Dec 2010 02:17:26 -0800 (PST) In-Reply-To: References: <98BEE0A8-9BC4-4644-9867-DE69872F329C@gmail.com> Date: Thu, 2 Dec 2010 11:17:26 +0100 Message-ID: Subject: Re: something wrong with hbase mapreduce From: Lars George To: user@hbase.apache.org Content-Type: text/plain; charset=Big5 Content-Transfer-Encoding: quoted-printable So you are using explicit time stamps for the put calls? Is this related to https://issues.apache.org/jira/browse/HBASE-3300 by any chance? You have to be extra careful with explicit timestamps as newer deletes can mask readding puts that have an older timestamp. Try this: 1. Do the MR job 2. Do the delete from the shell 3. Check that it was deleted from the shell 4. Run a major compaction of the table on the shell (e.g. "major_compact ") 5. Re-run the MR job 6. Check if the value is there again. And finally let us know here :) Lars On Thu, Dec 2, 2010 at 2:48 AM, =B1=E7=B4=BA=A9=FA wro= te: > 0.20.6 > > 2010/12/2 Lars George > >> What version of HBase are you using? >> >> On Dec 1, 2010, at 9:24, =B1=E7=B4=BA=A9=FA wrote: >> >> > i found that if i didnt control timestamp of the put >> > mapreduce can run, otherwise just one time mapreduce. >> > the question is i scan by timestamp to get my data >> > so to put timestamp is my scan thing. >> > >> > any ideas ? thanks. >> > >> > 2010/12/1 =B1=E7=B4=BA=A9=FA >> > >> >> Hi,i found a problem in my hbase mapreduce case. >> >> >> >> when first running mapreduce TableMapReduceUtil runs ok. >> >> >> >> and i use hbase shell to delete some data from the table that mapredu= ce >> one >> >> . >> >> >> >> then ran mapreduce to insert some new data. >> >> >> >> no thing data changed, mapreduce didnt work. >> >> >> >> after that i drop the table and recreate it >> >> >> >> run mapreduce again ,data inserted successful. >> >> >> >> what happen to mapreduce . >> >> >> >> Is it only can insert table just one time? >> >> >> >