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 C2432FE3A for ; Fri, 29 Mar 2013 03:27:29 +0000 (UTC) Received: (qmail 89792 invoked by uid 500); 29 Mar 2013 03:27:27 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 89433 invoked by uid 500); 29 Mar 2013 03:27:26 -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 89387 invoked by uid 99); 29 Mar 2013 03:27:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 03:27:24 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Mar 2013 03:27:18 +0000 Received: by mail-la0-f43.google.com with SMTP id ek20so252610lab.2 for ; Thu, 28 Mar 2013 20:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=fjDvQi7eY+6KC9KdD+bWEjydjL5yRe1Ap6tACkoMEpA=; b=WJxpAUtJFnCKu8qlUYYWkariw3ZihUpDAAZFYjHntS8JNI95fGqON9hoKEwnDE7YZq S2sbfNZOcFsOl2RgG0+45DLsdYw2XzgQlVxro4aZ+k+G/2Cg6BhcA1Oy82G5zE8PMCom SajuGOOraUgDIo7/yTQ31bt33ATMyf5iqZeCzUh6RZ1UYz1vDKTGftWyLFkGcQzXKdPN C/TgL4EvPTXvP8M9lOReEue3XQ+5YrKmFxeo1EiOTbR71rQex7PtnGijKTtNDZ5BAZPI e0ipspTqDFzCXenJ5ktIkKA/T0ftXL/kBairjChSBw1wkV05hnnrs7dx+F+hxaOBpeJr Nj2w== MIME-Version: 1.0 X-Received: by 10.112.5.138 with SMTP id s10mr680352lbs.73.1364527617991; Thu, 28 Mar 2013 20:26:57 -0700 (PDT) Received: by 10.112.84.133 with HTTP; Thu, 28 Mar 2013 20:26:57 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Mar 2013 20:26:57 -0700 Message-ID: Subject: Re: coprocessor is timing out in 0.94 From: Ted Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=14dae94ed821f4e94604d907d77c X-Virus-Checked: Checked by ClamAV on apache.org --14dae94ed821f4e94604d907d77c Content-Type: text/plain; charset=ISO-8859-1 Saurabh: I guess you are aware of the following for SingleColumnValueFilter, but just in case: * To prevent the entire row from being emitted if the column is not found * on a row, use {@link #setFilterIfMissing}. On Thu, Mar 28, 2013 at 6:51 PM, Agarwal, Saurabh wrote: > Ted, > > Thanks for response. > > Here is the filter we are using - > SingleColumnValueFilter(Bytes.toBytes(columnFamily), > Bytes.toBytes(columnQualifier), CompareFilter.CompareOp.EQUAL, new > RegexStringComparator("(?i)"+"keyword")); > > The thread dump at different points show that coprocessor is getting > called. Also logs showed it keep processing. But the speed is much slower > compare to 0.92. > > Regards, > Saurabh. > > -----Original Message----- > From: Ted Yu [mailto:yuzhihong@gmail.com] > Sent: Thursday, March 28, 2013 6:57 PM > To: user@hbase.apache.org > Subject: Re: coprocessor is timing out in 0.94 > > bq. I checked thread dump > > If there was no exception in region server logs, thread dump of region > server when your coprocessor was running would reveal where it got stuck. > > From your description below, looks like you can utilize HBASE-5416 Improve > performance of scans with some kind of filters. > > bq. to apply the filter on one of the column > > Basically this column is the essential column. > > Cheers > > On Thu, Mar 28, 2013 at 3:22 PM, Ted Yu wrote: > > > bq. when I removed the filter, it ran fine in 0.94 > > > > Can you disclose more information about your filter ? > > > > BTW 0.94.6 was just released which is fully compatible with 0.94.2 > > > > Cheers > > > > On Thu, Mar 28, 2013 at 3:18 PM, Agarwal, Saurabh < > > saurabh.agarwal@citi.com> wrote: > > > >> Hi, > >> > >> We are in process of migrating from 0.92.1 to 0.94.2. A coprocessor > >> was running fine in 0.92. After migrating to 0.94, the client is > >> timing out (java.net.SocketTimeoutException). We are using > >> coprocessor to apply the filter on one of the column and return the > >> columns that match with that filter criteria. I checked thread dump, > >> region server, web UI, logs. There is no error or exception. One > >> thing I noticed that when I removed the filter, it ran fine in 0.94 as > well. > >> > >> Please advise if there is any specific setting we need to make in 0.94. > >> > >> Thanks, > >> Saurabh. > >> > > > > > --14dae94ed821f4e94604d907d77c--