Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates
 209.85.220.169 as permitted sender)
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: 
 <6C5C1804772DB944BA88A0DC48D338DA0B44EE7D@dct-mail.sanjose.telcontar.com>
References: <Acx3weCWpPfdIqltQVypLx6IJ1WLAA==>
	<6C5C1804772DB944BA88A0DC48D338DA0B44EE7D@dct-mail.sanjose.telcontar.com>
Date: Mon, 26 Sep 2011 12:14:42 -0700
Message-ID: 
 <CAGpTDNfjroZ7TAzZewrnw2TmzpCNCtoTTQ3EPHHf9rfb8vJsog@mail.gmail.com>
Subject: Re: SocketChannel exception
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

(late answer, sorry)

60 seconds is a long time to be left hanging, my first guess would be
to look for signs of GC in that region server and make sure you don't
swap at all. You could go further and jstack the RS while it's
hanging, maybe you'll see that all the handlers are busy, but even
then if they take that long to process it might be due what I
previously mentioned.

J-D

On Tue, Sep 20, 2011 at 11:19 AM, Rohit Nigam <rnigam@decarta.com> wrote:
> Hi Guys
>
> I am getting this exception while running the job in the reducer phase.
> The reducer =A0retrieves =A0a data structure =A0for a key from hbase =A0a=
nd then
> populates it and put =A0it back again. The exception says like this :--
>
>
>
> java.net.SocketTimeoutException: Call to x server /xx.xx.xx.xxx:60020
> failed on socket timeout exception: java.net.SocketTimeoutException:
> 60000 millis timeout while waiting for channel to be ready for read. ch
> : java.nio.channels.SocketChannel[connected local=3D/yy.yy.yy.yyy:44751
> remote=3D x server /xx.xx.xx.xxx:60020]
>
> java.net.SocketTimeoutException: 20000 millis timeout while waiting for
> channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=3Ddoop18.dt.sv4.decarta.com/10.241.8.238:60020]
>
> java.net.SocketTimeoutException: 20000 millis timeout while waiting for
> channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=3Ddoop18.dt.sv4.decarta.com/10.241.8.238:60020]
>
> java.net.SocketTimeoutException: 20000 millis timeout while waiting for
> channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=3Ddoop18.dt.sv4.decarta.com/10.241.8.238:60020]
>
> java.net.SocketTimeoutException: 20000 millis timeout while waiting for
> channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=3Ddoop18.dt.sv4.decarta.com/10.241.8.238:60020]
>
> java.net.SocketTimeoutException: 20000 millis timeout while waiting for
> channel to be ready for connect. ch :
> java.nio.channels.SocketChannel[connection-pending
> remote=3Ddoop18.dt.sv4.decarta.com/10.241.8.238:60020]
>
> java.net.SocketTimeoutException
>
>
>
> There is a lot of IO involved in the reducer phase as to talking with
> HBASE. Would really appreciate if somebody can shed some light as to
> when can this exception happen. Is it related to regionservers being too
> busy to cater the request?
>
>
>
> Thanks
>
> Rohit
>
>
>
>