Created
March 18, 2011 17:37
-
-
Save seigel/876508 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 2011-03-18 00:00:58,653 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server Responder, call multi(org.apache.hadoop.hbase.client.MultiAction@2fb65c0a) from 10.5.240.241:33574: output error | |
| 2011-03-18 00:00:58,653 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server handler 14 on 60020 caught: java.nio.channels.ClosedChannelException | |
| at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:126) | |
| at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324) | |
| at org.apache.hadoop.hbase.ipc.HBaseServer.channelWrite(HBaseServer.java:1339) | |
| at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.processResponse(HBaseServer.java:727) | |
| at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.doRespond(HBaseServer.java:792) | |
| at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1083) |
I think a couple of things fixed this.
One, we were leaking connections on a test we were performing. So we stopped that.
Two. We upgraded to a new version of hbase after that.
I think the main thing was saturating the connections to zookeeper.
James
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing this too when HBase is under heavy writes. Did you figure anything out on this?