hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: timing out for hdfs errors faster
Date Thu, 07 Apr 2011 17:28:40 GMT
On Thu, Apr 7, 2011 at 7:58 AM, Jack Levin <magnito@gmail.com> wrote:
> Hello, I get those errors sometimes:
>
> 2011-04-07 07:49:41,527 WARN org.apache.hadoop.hdfs.DFSClient: Failed
> to connect to /10.103.7.5:50010 for file
> /hbase/media_data/1c95bfcf0dd19800b1f44278627259ae/att/7725092577730365184
> for block 802538788372768807:java.net.SocketTimeoutException: 60000
> millis timeout while waiting for channel to be ready for read. ch :
> java.nio.channels.SocketChannel[connected local=/10.101.6.8:40801
> remote=/10.103.7.5:50010
>
> What would be configuration setting to shorten the timeout say to 5
> seconds?  What about retries (if any).
>

0.90.0 added a timeout to the RPC (See HBASE-3154  'HBase RPC should
support timeout').  The default is 60 seconds.  To change the config.,
set hbase.rpc.timeout.  Retries should be going on in the upper
layers.  As to why 60 seconds, my guess is that the author and
reviewer were being conservative.  Previous there was no timeout.

St.Ack

Mime
View raw message