Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 919559752 for ; Fri, 24 Aug 2012 01:28:38 +0000 (UTC) Received: (qmail 65894 invoked by uid 500); 24 Aug 2012 01:28:37 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 65843 invoked by uid 500); 24 Aug 2012 01:28:37 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 65835 invoked by uid 99); 24 Aug 2012 01:28:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2012 01:28:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qc0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2012 01:28:33 +0000 Received: by qcsd16 with SMTP id d16so1134078qcs.14 for ; Thu, 23 Aug 2012 18:28:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ONWgiK1iOqnrIpAnYi1fgQiEpEGjCA1jXRcTn124v4o=; b=QoEFnJ5kf41zO7Fy8N6hndUqFrb0SiDs3klRqkogr0StMYQHEuuC4tdnxLNfusfHKz XW3LWoxcyK6S0sgR9D/nEVGoubEkKpZLMDprhhyM8es8JUJg5TBoSSm6YUWzWoCItqwF Jcdm5wYM8LOvK24WQdRO7/mEwUthfWIry5RepiXIOWkumnKNBsEZVFjVY6Pbbi9Fxzlp N5tJV1wPcmM5y+FNGyG4Mk0Od6eFqfTDVMhM+iGJrlL+0TaHlLVmjaoKuQNNbYDXmZts 3Z7ylW85Ve+PtGHpDyTkAtfXB2cR4z5b6o1vfwnL/QRvZpJINtjc+sYAeBiYk/gC70/w 6Epw== MIME-Version: 1.0 Received: by 10.229.105.100 with SMTP id s36mr1690629qco.88.1345771692977; Thu, 23 Aug 2012 18:28:12 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.49.63.136 with HTTP; Thu, 23 Aug 2012 18:28:12 -0700 (PDT) In-Reply-To: <1345770654.40868.YahooMailNeo@web121702.mail.ne1.yahoo.com> References: <1345770324.77012.YahooMailNeo@web121704.mail.ne1.yahoo.com> <1345770654.40868.YahooMailNeo@web121702.mail.ne1.yahoo.com> Date: Thu, 23 Aug 2012 18:28:12 -0700 X-Google-Sender-Auth: ceFIXwOWnUuM_KYdP1Z09PlBtTk Message-ID: Subject: Re: HBase-0.94.2-SNAPSHOT Scanning Bug From: Jean-Daniel Cryans To: dev@hbase.apache.org, lars hofhansl Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org We tried reproducing on a local node but it doesn't show up. It did show as soon as we put it on our dev cluster. J-D On Thu, Aug 23, 2012 at 6:10 PM, lars hofhansl wrote: > It is interesting, though, because I have been running my local perf testing with this change included and have not seen this issue. > > -- Lars > > > > ----- Original Message ----- > From: lars hofhansl > To: "dev@hbase.apache.org" > Cc: > Sent: Thursday, August 23, 2012 6:05 PM > Subject: Re: HBase-0.94.2-SNAPSHOT Scanning Bug > > This: > > "IPC Server handler 43 on 10304" daemon prio=10 tid=0x00007f16b8b1f000 nid=0x6414 runnable [0x00007f16b47c6000] > java.lang.Thread.State: RUNNABLE > at org.apache.hadoop.hbase.KeyValue.createFirstOnRowColTS(KeyValue.java:1893) > at org.apache.hadoop.hbase.regionserver.StoreFileScanner.requestSeek(StoreFileScanner.java:310) > at org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:297) > at org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:256) > at org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:522) > - locked <0x00000006cec5bd88> (a org.apache.hadoop.hbase.regionserver.StoreScanner) > at org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:54) > at org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.requestSeek(NonLazyKeyValueScanner.java:38) > at org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:297) > at org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:256) > at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRow(HRegion.java:3508) > > points to my change: https://issues.apache.org/jira/browse/HBASE-6577 > > The trace is interesting: RegionScannerImpl.nextRow now seeks to the last KV in the row and then iterates as before. > However, then the reseek internally seeks to the first KV of the column, and somehow this interaction makes no progress forward. > > I'll revert that change. > > -- Lars > > > ________________________________ > From: Elliott Clark > To: dev@hbase.apache.org > Sent: Thursday, August 23, 2012 5:39 PM > Subject: HBase-0.94.2-SNAPSHOT Scanning Bug > > I recently tried to update one of our clusters to a version of 0.94.2 > seen here: https://github.com/stumbleupon/hbase/commits/su_prod_94 > > When doing that all of the nodes started taking all available cpu > time. Not much interesting was in the logs however jstacks looked > like this: http://pastebin.com/raw.php?i=fw6P5RKE Everything is > spinning in scans. A version of 0.94.1 works perfectly and reverting > solved all issues. I don't really have enough data to point at any > jira as the cause I was just wondering if anyone had some insight into > the few commits between 0.94.1 release and the head of the above > github that could cause scans to spin. > > Thanks >