Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    This was a bug at HBase 1.0.1, it has been patched, so an update to 1.0.2 or further should solve the problem. URL for the Jira thread: https://goo.gl/c5oa6f

Solutions on the web

via Stack Overflow by MrProper
, 1 year ago
Failed to fetch block from 1 locations. Most recent failure cause:
via Stack Overflow by Naresh
, 1 year ago
Failed to fetch block from 1 locations. Most recent failure cause:
via Stack Overflow by Fanooos
, 2 years ago
Failed to fetch block from 2 locations. Most recent failure cause:
via nabble.com by Unknown author, 2 years ago
Failed to fetch block from 2 locations. Most recent failure cause:
java.net.ConnectException: Connection refused: /192.168.99.101:35306	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:224)	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:289)	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)	at java.lang.Thread.run(Thread.java:745)