phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajit Bhingarkar <ajit.bhingar...@nielsen.com>
Subject Re: hbase.rpc.timeout issue
Date Thu, 15 Jun 2017 05:24:36 GMT
Hi,

We are using a java based client for phoenix, and there is no hbase
installation available on the client machine. During longer database
operations we are getting the error as below:

Error Code: 101, SQL State: 08000]
org.apache.phoenix.exception.PhoenixIOException:
Failed after attempts=36, exceptions:
Wed Jun 14 12:32:26 IST 2017, null, java.net.SocketTimeoutException:
callTimeout=60000, callDuration=79332: row '' on table
'D2O_OPTAL_MY.D2O_OPTAL_CELL_DIFF_REPORT' at region=D2O_OPTAL_MY.D2O_OPTAL_
CELL_DIFF_REPORT,,1497351811844.ebdeb51f81914e7ea2291e83e1ff6022., hostname=
tparhegapi008.enterprisenet.org,60020,1493969895840, seqNum=2

>From various references found through google it is clear that the
SocketTimeoutException is caused by default value of hbase.rpc.timeput
which is 60000 ms.

Can someone please help us configure this setting on the client side?
Same setting on the server side in hbase-site.xml has been set to 10
minutes, but looks like client is timing out the connection.

Thanks in advance for your help.

Regards,
Ajit


On Thu, Jun 15, 2017 at 10:47 AM, Ajit Bhingarkar <
ajit.bhingarkar@nielsen.com> wrote:

> Hi,
>
> We are using a java based client for phoenix, and there is no hbase
> installation available on the client machine. During longer database
> operations we are getting the error as below:
>
> Error Code: 101, SQL State: 08000]  org.apache.phoenix.exception.PhoenixIOException:
> Failed after attempts=36, exceptions:
> Wed Jun 14 12:32:26 IST 2017, null, java.net.SocketTimeoutException:
> callTimeout=60000, callDuration=79332: row '' on table
> 'D2O_OPTAL_MY.D2O_OPTAL_CELL_DIFF_REPORT' at
> region=D2O_OPTAL_MY.D2O_OPTAL_CELL_DIFF_REPORT,,1497351811844.
> ebdeb51f81914e7ea2291e83e1ff6022., hostname=tparhegapi008.
> enterprisenet.org,60020,1493969895840, seqNum=2
>
> From various references found through google it is clear that the
> SocketTimeoutException is caused by default value of hbase.rpc.timeput
> which is 60000 ms.
>
> Can someone please help us configure this setting on the client side?
> Same setting on the server side in hbase-site.xml has been set to 10
> minutes, but looks like client is timing out the connection.
>
> Thanks in advance for your help.
>
> Regards,
> Ajit
>
>

Mime
View raw message