# ES 0.19.0 errors **URL:** \ **Category:** Elasticsearch\ **Created:** [March 4, 2012, 9:31pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882 "2012-03-04T21:31:08Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Grant](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Grant](https://discuss.elastic.co/u/Grant)\ **Post date:** [March 4, 2012, 9:31pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/1 "2012-03-04T21:31:08Z")
We're seeing all kinds of these errors. Initially I thought I'd missed upgrading a node in the cluster, but that turns out not to have been the case. Any ideas? It's triggered with a query of /index/\_analyze? text=some\_text&analyzer=hashingFulltext. The weird part is that on initial cluster creation, this error isn't triggered. And in fact our staging env isn't throwing this either, but there are only a handful of indexes there. Ideas? [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- es-r01] failed to execute [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] [inet[/10.180.35.110:9300]][indices/analyze/s] Caused by: java.io.IOException: Expected handle header, got [111] at org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStreamInput.java: 63) at org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(AnalyzeRequest.java: 150) at org.elasticsearch.action.support.single.custom.TransportSingleCustomOperationAction $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction.java: 359) at org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java: 313) at org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChannelHandler.java: 217) at org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java: 141) at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java: 95) at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java: 75) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java: 558) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: 777) at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java: 74) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java: 558) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java: 553) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java: 268) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java: 255) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java: 343) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java: 274) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java: 194) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java: 102) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker $1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) ---
**Author:** ![Grant](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Grant](https://discuss.elastic.co/u/Grant)\ **Post date:** [March 4, 2012, 9:40pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/2 "2012-03-04T21:40:00Z")
Also a lot of this: [2012-03-04 16:02:30,936][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [3435365] and action [indices/analyze/s], resetting [2012-03-04 16:02:30,943][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [4273675] and action [indices/analyze/s], resetting [2012-03-04 16:02:30,949][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [3380164] and action [indices/analyze/s], resetting [2012-03-04 16:02:30,971][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [3526609] and action [indices/analyze/s], resetting [2012-03-04 16:02:30,983][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [2030640] and action [indices/analyze/s], resetting [2012-03-04 16:02:31,002][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [3435372] and action [indices/analyze/s], resetting [2012-03-04 16:02:31,008][WARN][transport.netty] [prod-es- r01] Message not fully read (request) for [4273682] and action [indices/analyze/s], resetting ---
**Author:** ![Matthew\_A\_Brown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matthew_a_brown/32/2699_2.png) [@Matthew\_A\_Brown](https://discuss.elastic.co/u/Matthew_A_Brown)\ **Post date:** [March 4, 2012, 9:41pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/3 "2012-03-04T21:41:53Z")
Just to clarify -- the hashingFulltext analyzer is a custom one we built, but we see this even when performing \_analyze requests with the standard analyzer etc. We also don't see this when making \_analyze requests to the root / \_analyze endpoint, only when making requests to \_analyze on a specific index. On Mar 4, 4:31 pm, Grant [gr...@brewster.com](mailto:gr...@brewster.com) wrote: > We're seeing all kinds of these errors. Initially I thought I'd missed > upgrading a node in the cluster, but that turns out not to have been > the case. Any ideas? It's triggered with a query of /index/\_analyze? > text=some\_text&analyzer=hashingFulltext. The weird part is that on > initial cluster creation, this error isn't triggered. And in fact our > staging env isn't throwing this either, but there are only a handful > of indexes there. > > Ideas? > > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > es-r01] failed to execute > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > [inet[/10.180.35.110:9300]][indices/analyze/s] > Caused by: java.io.IOException: Expected handle header, got [111] > at > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStream Input.java: > 63) > at > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(Anal yzeRequest.java: > 150) > at > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperati onAction > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction. java: > 359) > at > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(Messa geChannelHandler.java: > 313) > at > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChan nelHandler.java: > 217) > at > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageC hannelHandler.java: > 141) > at > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(Mes sageChannelHandler.java: > 95) > at > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java: > 75) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > 558) > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > 777) > at > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java: > 74) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > 558) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > 553) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > 268) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > 255) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java: > 343) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java: > 274) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava: > 194) > at > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java: > 102) > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > $1.run(DeadLockProofWorker.java:42) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [March 5, 2012, 9:47am UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/4 "2012-03-05T09:47:23Z")
On Sun, 2012-03-04 at 13:31 -0800, Grant wrote: > We're seeing all kinds of these errors. Initially I thought I'd missed > upgrading a node in the cluster, but that turns out not to have been > the case. Any ideas? It's triggered with a query of /index/\_analyze? > text=some\_text&analyzer=hashingFulltext. The weird part is that on > initial cluster creation, this error isn't triggered. And in fact our > staging env isn't throwing this either, but there are only a handful > of indexes there. > > Ideas? Looks like you have mixed different versions of ES, I think clint > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > es-r01] failed to execute > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > [inet[/10.180.35.110:9300]][indices/analyze/s] > Caused by: java.io.IOException: Expected handle header, got [111] > at > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStreamInput.java: > 63) > at > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(AnalyzeRequest.java: > 150) > at > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperationAction > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction.java: > 359) > at > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java: > 313) > at > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChannelHandler.java: > 217) > at > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageChannelHandler.java: > 141) > at > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java: > 95) > at > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java: > 75) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java: > 558) > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > 777) > at > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java: > 74) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java: > 558) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java: > 553) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java: > 268) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java: > 255) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java: > 343) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java: > 274) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java: > 194) > at > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java: > 102) > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > $1.run(DeadLockProofWorker.java:42) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![Grant](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Grant](https://discuss.elastic.co/u/Grant)\ **Post date:** [March 5, 2012, 12:10pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/5 "2012-03-05T12:10:26Z")
Turns out that was the case, although the cluster itself was all 0.19. Because we're using unicast and running logstash on these hosts, there was was some cross connection going on that shouldn't have been due to port overlap. On Mar 5, 4:47 am, Clinton Gormley [cl...@traveljury.com](mailto:cl...@traveljury.com) wrote: > On Sun, 2012-03-04 at 13:31 -0800, Grant wrote: > > > We're seeing all kinds of these errors. Initially I thought I'd missed > > upgrading a node in the cluster, but that turns out not to have been > > the case. Any ideas? It's triggered with a query of /index/\_analyze? > > text=some\_text&analyzer=hashingFulltext. The weird part is that on > > initial cluster creation, this error isn't triggered. And in fact our > > staging env isn't throwing this either, but there are only a handful > > of indexes there. > > > Ideas? > > Looks like you have mixed different versions of ES, I think > > clint > > > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > > es-r01] failed to execute > > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > > [inet[/10.180.35.110:9300]][indices/analyze/s] > > Caused by: java.io.IOException: Expected handle header, got [111] > > at > > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStream Input.java: > > 63) > > at > > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(Anal yzeRequest.java: > > 150) > > at > > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperati onAction > > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction. java: > > 359) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(Messa geChannelHandler.java: > > 313) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChan nelHandler.java: > > 217) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageC hannelHandler.java: > > 141) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(Mes sageChannelHandler.java: > > 95) > > at > > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java: > > 75) > > at > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > 558) > > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > > 777) > > at > > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java: > > 74) > > at > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > 558) > > at > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > 553) > > at > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > 268) > > at > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > 255) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java: > > 343) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java: > > 274) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava: > > 194) > > at > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java: > > 102) > > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > > $1.run(DeadLockProofWorker.java:42) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > > Source) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![Grant](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Grant](https://discuss.elastic.co/u/Grant)\ **Post date:** [March 5, 2012, 12:16pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/6 "2012-03-05T12:16:46Z")
It does seem to me though that ES should fail to start if you're specifically defining transport.port: 9300, but something else is listening on that address already. Instead it selected the next available port. On Mar 5, 4:47 am, Clinton Gormley [cl...@traveljury.com](mailto:cl...@traveljury.com) wrote: > On Sun, 2012-03-04 at 13:31 -0800, Grant wrote: > > > We're seeing all kinds of these errors. Initially I thought I'd missed > > upgrading a node in the cluster, but that turns out not to have been > > the case. Any ideas? It's triggered with a query of /index/\_analyze? > > text=some\_text&analyzer=hashingFulltext. The weird part is that on > > initial cluster creation, this error isn't triggered. And in fact our > > staging env isn't throwing this either, but there are only a handful > > of indexes there. > > > Ideas? > > Looks like you have mixed different versions of ES, I think > > clint > > > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > > es-r01] failed to execute > > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > > [inet[/10.180.35.110:9300]][indices/analyze/s] > > Caused by: java.io.IOException: Expected handle header, got [111] > > at > > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStream Input.java: > > 63) > > at > > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(Anal yzeRequest.java: > > 150) > > at > > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperati onAction > > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction. java: > > 359) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(Messa geChannelHandler.java: > > 313) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChan nelHandler.java: > > 217) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageC hannelHandler.java: > > 141) > > at > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(Mes sageChannelHandler.java: > > 95) > > at > > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java: > > 75) > > at > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > 558) > > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > > 777) > > at > > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java: > > 74) > > at > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > 558) > > at > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > 553) > > at > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > 268) > > at > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > 255) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java: > > 343) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java: > > 274) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava: > > 194) > > at > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java: > > 102) > > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > > $1.run(DeadLockProofWorker.java:42) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > > Source) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [March 5, 2012, 2:53pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/7 "2012-03-05T14:53:07Z")
Yes, thats how it works by default, if port 9300 is busy, it will try the next one. This allows to easily start several nodes on the same machine, or have a client and a server running on the same machine. On Monday, March 5, 2012 at 2:16 PM, Grant wrote: > It does seem to me though that ES should fail to start if you're > specifically defining transport.port: 9300, but something else is > listening on that address already. Instead it selected the next > available port. > > On Mar 5, 4:47 am, Clinton Gormley \<[cl...@traveljury.com](mailto:cl...@traveljury.com) ([http://traveljury.com](http://traveljury.com))\> wrote: > > > On Sun, 2012-03-04 at 13:31 -0800, Grant wrote: > > > > > We're seeing all kinds of these errors. Initially I thought I'd missed > > > upgrading a node in the cluster, but that turns out not to have been > > > the case. Any ideas? It's triggered with a query of /index/\_analyze? > > > text=some\_text&analyzer=hashingFulltext. The weird part is that on > > > initial cluster creation, this error isn't triggered. And in fact our > > > staging env isn't throwing this either, but there are only a handful > > > of indexes there. > > > > > Ideas? > > > > Looks like you have mixed different versions of ES, I think > > > > clint > > > > > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > > > es-r01] failed to execute > > > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > > > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > > > [inet[/10.180.35.110:9300]][indices/analyze/s] > > > Caused by: java.io.IOException: Expected handle header, got [111] > > > at > > > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStream Input.java: > > > 63) > > > at > > > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(Anal yzeRequest.java: > > > 150) > > > at > > > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperati onAction > > > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction. java: > > > 359) > > > at > > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(Messa geChannelHandler.java: > > > 313) > > > at > > > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChan nelHandler.java: > > > 217) > > > at > > > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageC hannelHandler.java: > > > 141) > > > at > > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(Mes sageChannelHandler.java: > > > 95) > > > at > > > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java: > > > 75) > > > at > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > 558) > > > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > > > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > > > 777) > > > at > > > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java: > > > 74) > > > at > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > 558) > > > at > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > 553) > > > at > > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > > 268) > > > at > > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > > 255) > > > at > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java: > > > 343) > > > at > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java: > > > 274) > > > at > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava: > > > 194) > > > at > > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java: > > > 102) > > > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > > > $1.run(DeadLockProofWorker.java:42) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > > > Source) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [March 5, 2012, 3:04pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/8 "2012-03-05T15:04:51Z")
Hint: to avoid the clutter of several ES versions on the same server hardware, I use always a cluster name with the version in the setup, e.g. "elasticsearch-0.18.5", instead of default "elasticsearch". > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Jörg On Mar 5, 3:53 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Yes, thats how it works by default, if port 9300 is busy, it will try the next one. This allows to easily start several nodes on the same machine, or have a client and a server running on the same machine. > > On Monday, March 5, 2012 at 2:16 PM, Grant wrote: > > > It does seem to me though that ES should fail to start if you're > > specifically defining transport.port: 9300, but something else is > > listening on that address already. Instead it selected the next > > available port. > > > On Mar 5, 4:47 am, Clinton Gormley \<[cl...@traveljury.com](mailto:cl...@traveljury.com) ([http://traveljury.com](http://traveljury.com))\> wrote: > > > > > On Sun, 2012-03-04 at 13:31 -0800, Grant wrote: > > > > > > > We're seeing all kinds of these errors. Initially I thought I'd missed > > > > upgrading a node in the cluster, but that turns out not to have been > > > > the case. Any ideas? It's triggered with a query of /index/\_analyze? > > > > text=some\_text&analyzer=hashingFulltext. The weird part is that on > > > > initial cluster creation, this error isn't triggered. And in fact our > > > > staging env isn't throwing this either, but there are only a handful > > > > of indexes there. > > > > > Ideas? > > > > Looks like you have mixed different versions of ES, I think > > > > clint > > > > > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > > > > es-r01] failed to execute > > > > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > > > > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > > > > [inet[/10.180.35.110:9300]][indices/analyze/s] > > > > Caused by: java.io.IOException: Expected handle header, got [111] > > > > at > > > > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStream Input.java: > > > > 63) > > > > at > > > > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(Anal yzeRequest.java: > > > > 150) > > > > at > > > > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperati onAction > > > > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction. java: > > > > 359) > > > > at > > > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(Messa geChannelHandler.java: > > > > 313) > > > > at > > > > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChan nelHandler.java: > > > > 217) > > > > at > > > > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageC hannelHandler.java: > > > > 141) > > > > at > > > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(Mes sageChannelHandler.java: > > > > 95) > > > > at > > > > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java: > > > > 75) > > > > at > > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > > 558) > > > > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > > > > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > > > > 777) > > > > at > > > > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java: > > > > 74) > > > > at > > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > > 558) > > > > at > > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > > 553) > > > > at > > > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > > > 268) > > > > at > > > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > > > 255) > > > > at > > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java: > > > > 343) > > > > at > > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java: > > > > 274) > > > > at > > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava: > > > > 194) > > > > at > > > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java: > > > > 102) > > > > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > > > > $1.run(DeadLockProofWorker.java:42) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > > > > Source) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > > > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [March 6, 2012, 5:21pm UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/9 "2012-03-06T17:21:20Z")
That is a great suggestion. We need a Wiki/cookbook to catalog all these great tiny solutions. -- Ivan On Mon, Mar 5, 2012 at 7:04 AM, jprante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Hint: to avoid the clutter of several ES versions on the same server > hardware, I use always a cluster name with the version in the setup, > e.g. "elasticsearch-0.18.5", instead of default "elasticsearch". > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/discovery/index.html) > > Jörg > > On Mar 5, 3:53 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Yes, thats how it works by default, if port 9300 is busy, it will try the next one. This allows to easily start several nodes on the same machine, or have a client and a server running on the same machine. > > > > On Monday, March 5, 2012 at 2:16 PM, Grant wrote: > > > > > It does seem to me though that ES should fail to start if you're > > > specifically defining transport.port: 9300, but something else is > > > listening on that address already. Instead it selected the next > > > available port. > > > > > On Mar 5, 4:47 am, Clinton Gormley \<[cl...@traveljury.com](mailto:cl...@traveljury.com) ([http://traveljury.com](http://traveljury.com))\> wrote: > > > > > > > On Sun, 2012-03-04 at 13:31 -0800, Grant wrote: > > > > > > > > > We're seeing all kinds of these errors. Initially I thought I'd missed > > > > > upgrading a node in the cluster, but that turns out not to have been > > > > > the case. Any ideas? It's triggered with a query of /index/\_analyze? > > > > > text=some\_text&analyzer=hashingFulltext. The weird part is that on > > > > > initial cluster creation, this error isn't triggered. And in fact our > > > > > staging env isn't throwing this either, but there are only a handful > > > > > of indexes there. > > > > > > > Ideas? > > > > > > Looks like you have mixed different versions of ES, I think > > > > > > clint > > > > > > > [2012-03-04 20:02:46,561][DEBUG][action.admin.indices.analyze] [prod- > > > > > es-r01] failed to execute > > > > > [org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest@10d72878] > > > > > org.elasticsearch.transport.RemoteTransportException: [prod-es-r04] > > > > > [inet[/10.180.35.110:9300]][indices/analyze/s] > > > > > Caused by: java.io.IOException: Expected handle header, got [111] > > > > > at > > > > > org.elasticsearch.common.io.stream.HandlesStreamInput.readUTF(HandlesStream Input.java: > > > > > 63) > > > > > at > > > > > org.elasticsearch.action.admin.indices.analyze.AnalyzeRequest.readFrom(Anal yzeRequest.java: > > > > > 150) > > > > > at > > > > > org.elasticsearch.action.support.single.custom.TransportSingleCustomOperati onAction > > > > > $ShardSingleOperationRequest.readFrom(TransportSingleCustomOperationAction. java: > > > > > 359) > > > > > at > > > > > org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(Messa geChannelHandler.java: > > > > > 313) > > > > > at > > > > > org.elasticsearch.transport.netty.MessageChannelHandler.process(MessageChan nelHandler.java: > > > > > 217) > > > > > at > > > > > org.elasticsearch.transport.netty.MessageChannelHandler.callDecode(MessageC hannelHandler.java: > > > > > 141) > > > > > at > > > > > org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(Mes sageChannelHandler.java: > > > > > 95) > > > > > at > > > > > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleU pstream(SimpleChannelUpstreamHandler.java: > > > > > 75) > > > > > at > > > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > > > 558) > > > > > at org.elasticsearch.common.netty.channel.DefaultChannelPipeline > > > > > $DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java: > > > > > 777) > > > > > at > > > > > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChann elsHandler.java: > > > > > 74) > > > > > at > > > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > > > 558) > > > > > at > > > > > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream( DefaultChannelPipeline.java: > > > > > 553) > > > > > at > > > > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > > > > 268) > > > > > at > > > > > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channel s.java: > > > > > 255) > > > > > at > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker. java: > > > > > 343) > > > > > at > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelected Keys(NioWorker.java: > > > > > 274) > > > > > at > > > > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.j ava: > > > > > 194) > > > > > at > > > > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenami ngRunnable.java: > > > > > 102) > > > > > at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker > > > > > $1.run(DeadLockProofWorker.java:42) > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > > > > > Source) > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > > > > > at java.lang.Thread.run(Unknown Source) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:37am UTC](https://discuss.elastic.co/t/es-0-19-0-errors/6882/10 "2017-07-06T03:37:10Z")