Do you have a lot of data? This means the scanner took too long on the server
and the client essentially timed out.
PrefixFilter does not actually skip ahead to the first row in question. You
always have to also set the scanner's startRow to the first row you care about
(i.e. the prefix).In you
We've had jobs dying because of this, a quick workaround was in our case to
decrease hbase.client.scanner.caching (to 100) and increase
hbase.rpc.timeout and hbase.client.scanner.timeout.period
(to 45 and 30).
On 25 March 2015 at 14:36, Talat Uyarer wrote:
> Hi,
>
> I use HBase 0.98.6-cd
Hi,
I use HBase 0.98.6-cdh5.3.2.
Only one regionserver has some warn logs. like this:
2:31:29.312 PMWARNorg.apache.hadoop.ipc.RpcServer
RpcServer.respondercallId: 1456110 service: ClientService methodName:
Scan size: 24 connection: 192.168.0.10:47064: output error
2:31:29.313 PMWARNorg.apache.
Also, which HBase version is it?
2015-03-25 9:47 GMT-04:00 ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com>:
> Can you see if there is any exception in the Regionserver logs?
>
> On Wed, Mar 25, 2015 at 2:17 PM, Talat Uyarer wrote:
>
> > Hi all,
> >
> > I try to use Prefix Filter on hbas
Can you see if there is any exception in the Regionserver logs?
On Wed, Mar 25, 2015 at 2:17 PM, Talat Uyarer wrote:
> Hi all,
>
> I try to use Prefix Filter on hbase shell. It throws an exception. I
> do not understand its reason. Could you help me ?
>
> scan 'table1',{FILTER => "PrefixFilter('
