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:yuzhih...@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 <yuzhih...@gmail.com> 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.agar...@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.
>>
>
>
