Exception in netty while indexing, :(

Antonio_Lobato · July 28, 2011, 3:00pm

Hi everyone!

While trying to index some really big documents into an Elasticsearch
cluster, we received the following error:

[2011-07-28 01:24:22,183][WARN ][http.netty ]
[Damballah] Caught exception while handling client http traffic,
closing connection
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
An HTTP line is larger than 4096 bytes.
at
org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.readLine(HttpMessageDecoder.java:
592)
at
org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:
191)
at
org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:
107)
at
org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:
470)
at
org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:
443)
at
org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
80)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
545)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline
$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:
754)
at
org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:
65)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
545)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
540)
at
org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:
274)
at
org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:
261)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:
349)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:
280)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:
200)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:
108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker
$1.run(DeadLockProofWorker.java:44)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1110)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Ideas? Thanks!

kimchy · July 28, 2011, 3:18pm

How are you indexing data? It seems like an http header line was sent that
is bigger than 4096?

On Thu, Jul 28, 2011 at 6:00 PM, Antonio Lobato aj.lobato@gmail.com wrote:

Hi everyone!

While trying to index some really big documents into an Elasticsearch
cluster, we received the following error:

[2011-07-28 01:24:22,183][WARN ][http.netty ]
[Damballah] Caught exception while handling client http traffic,
closing connection
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
An HTTP line is larger than 4096 bytes.
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.readLine(HttpMessageDecoder.java:
592)
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:
191)
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:
107)
at

org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:
470)
at

org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:
443)
at

org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
80)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
545)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline
$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:
754)
at

org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:
65)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
545)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
540)
at

org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:
274)
at

org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:
261)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:
349)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:
280)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:
200)
at

org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:
108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker
$1.run(DeadLockProofWorker.java:44)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1110)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Ideas? Thanks!

kimchy · July 28, 2011, 3:34pm

Still strange that you get it, but, I added options to allow to control it:
Http Transport: Allow to configure `max_header_size`, `max_initial_line_length`, and `max_chunk_size` · Issue #1174 · elastic/elasticsearch · GitHub.

On Thu, Jul 28, 2011 at 6:18 PM, Shay Banon kimchy@gmail.com wrote:

How are you indexing data? It seems like an http header line was sent that
is bigger than 4096?

On Thu, Jul 28, 2011 at 6:00 PM, Antonio Lobato aj.lobato@gmail.comwrote:

Hi everyone!

While trying to index some really big documents into an Elasticsearch
cluster, we received the following error:

[2011-07-28 01:24:22,183][WARN ][http.netty ]
[Damballah] Caught exception while handling client http traffic,
closing connection
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
An HTTP line is larger than 4096 bytes.
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.readLine(HttpMessageDecoder.java:
592)
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:
191)
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:
107)
at

org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:
470)
at

org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:
443)
at

org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:
80)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
545)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline
$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:
754)
at

org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:
65)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
545)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:
540)
at

org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:
274)
at

org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:
261)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:
349)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:
280)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:
200)
at

org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:
108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker
$1.run(DeadLockProofWorker.java:44)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1110)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Ideas? Thanks!

Antonio_Lobato · July 28, 2011, 9:03pm

We're indexing using a custom written REST client. I'm actually not
quite sure why the header sent was larger than 4096. I'll
investigate.

Thanks though!

On Jul 28, 11:34 am, Shay Banon kim...@gmail.com wrote:

Still strange that you get it, but, I added options to allow to control it:Http Transport: Allow to configure `max_header_size`, `max_initial_line_length`, and `max_chunk_size` · Issue #1174 · elastic/elasticsearch · GitHub.

On Thu, Jul 28, 2011 at 6:18 PM, Shay Banon kim...@gmail.com wrote:

How are you indexing data? It seems like an http header line was sent that
is bigger than 4096?

On Thu, Jul 28, 2011 at 6:00 PM, Antonio Lobato aj.lob...@gmail.comwrote:

Hi everyone!

While trying to index some really big documents into an Elasticsearch
cluster, we received the following error:

[2011-07-28 01:24:22,183][WARN ][http.netty ]
[Damballah] Caught exception while handling client http traffic,
closing connection
org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException:
An HTTP line is larger than 4096 bytes.
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.readLi ne(HttpMessageDecoder.java:
592)
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode (HttpMessageDecoder.java:
191)
at

org.elasticsearch.common.netty.handler.codec.http.HttpMessageDecoder.decode (HttpMessageDecoder.java:
107)
at

org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDe code(ReplayingDecoder.java:
470)
at

org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messag eReceived(ReplayingDecoder.java:
443)
at

org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java:
80)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java:
545)
at
org.elasticsearch.common.netty.channel.DefaultChannelPipeline
$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:
754)
at

org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java:
65)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java:
545)
at

org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java:
540)
at

org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java:
274)
at

org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java:
261)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java:
349)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java:
280)
at

org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava:
200)
at

org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java:
108)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker
$1.run(DeadLockProofWorker.java:44)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1110)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Ideas? Thanks!

Topic		Replies	Views
Caught exception while handling client http traffic, closing connection 1.7.4 Elasticsearch	2	2237	March 17, 2017
[elasticsearch.server][WARN] caught exception while handling client http traffic, closing connection Netty4HttpChannel Elasticsearch	1	55	August 21, 2024
Out of memory/heap Elasticsearch	3	963	July 6, 2017
Max doc size for indexing over HTTP Elasticsearch	2	1387	July 6, 2017
Exceptions in the log in ElasticSearch to 5.6.9 Elasticsearch	4	550	July 24, 2018

Exception in netty while indexing, :(

Related Topics