Support Questions
Find answers, ask questions, and share your expertise

web.DatanodeHttpServer (SimpleHttpProxyHandler.java:exceptionCaught(147)) - Proxy for / failed.

Explorer

I see these INFO messages frequently in datanode logs on a cluster running HDP 2.3.2. I don't see them in logs on a cluster running HDP 2.1.10. What are they trying to tell me?

4 REPLIES 4

@Geoff Holmes

I do see those in my cluster and I noticed that it happened during the server restart/network down. I would ignore it if it's not causing any outage or cluster downtime. For details , you can check out this

2015-11-21 15:51:12,355 INFO web.DatanodeHttpServer (SimpleHttpProxyHandler.java:exceptionCaught(147)) - Proxy for / failed. cause:

java.io.IOException: Connection reset by peer

at sun.nio.ch.FileDispatcherImpl.read0(Native Method)

at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)

at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)

at sun.nio.ch.IOUtil.read(IOUtil.java:192)

at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)

at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:446)

at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)

at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:225)

at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)

at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)

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:116)

at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)

at java.lang.Thread.run(Thread.java:745)


screen-shot-2016-01-17-at-31829-pm.png

Mentor

@Geoff Holmes are you still having problems with this? Can you provide your own solution or accept best answer?

Rising Star

The error is benign, it just means the client disconnect after finish writing. The issue has been fixed in latest HDP 2.5.

New Contributor

but I am till seeing the same on HDP 2.6.2.0, and it happens every a few minutes when nothing is running on the cluster