Bad disk or network?
Anything in the logs (HBase, HDFS, and System logs)?
HBase 0.94, still?The easiest way to just kill the region servers, the others
will pick up the regions.
-- Lars
From: Ted Tuttle <t...@mentacapital.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Cc: Development <developm...@mentacapital.com>
Sent: Wednesday, December 3, 2014 7:13 AM
Subject: client timeout
Hello-
We are seeing recurring timeouts in communications with one our RSs. The error
we see in our logs is:
Caused by: java.net.SocketTimeoutException: Call to <rs host>./<rs ip>:<port>
failed on socket timeout exceptio\
n: java.net.SocketTimeoutException: 120000 millis timeout while waiting for
channel to be ready for read. ch : java.nio.channels.S\
ocketChannel[connected local=/<client ip>:<port> remote=<rs host>./<rs
ip>:<port>]
at
org.apache.hadoop.hbase.ipc.HBaseClient.wrapException(HBaseClient.java:1043)
at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1016)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Invoker.invoke(WritableRpcEngine.java:87)
at com.sun.proxy.$Proxy9.multi(Unknown Source)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$3$1.call(HConnectionManager.java:1537)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$3$1.call(HConnectionManager.java:1535)
at
org.apache.hadoop.hbase.client.ServerCallable.withoutRetries(ServerCallable.java:229)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$3.call(HConnectionManager.java:1544)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$3.call(HConnectionManager.java:1532)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Any ideas on what could be wrong w/ this RS? The RS is not unusually busy.
Thanks,
Ted
