Seeing new exception in latest master

Samuel_Doyle · July 12, 2010, 7:08pm

Hi, I just updated today and now I'm seeing the following exception in ES on
startup.

[12:02:30,876][WARN ][discovery.zen.publish ] [Zip-Zap] failed to send
cluster state to [[Agent
Zero][bd671b76-eb40-4481-87b2-c9a479f5cc1f][inet[/192.168.22.131:9301]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...
org.elasticsearch.transport.RemoteTransportException: [Agent
Zero][inet[/192.168.22.131:9301]][discovery/zen/publish]
Caused by: java.lang.IndexOutOfBoundsException
at
org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:52)
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:100)
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:70)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readBlockSet(ClusterBlocks.java:265)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readClusterBlocks(ClusterBlocks.java:233)
at
org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:220)
at
org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequest.readFrom(PublishClusterStateAction.java:90)
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:170)
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:80)
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.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
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:51)
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:281)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Samuel_Doyle · July 12, 2010, 7:17pm

Hi, sorry this is a false alarm, must make a mental note to always update
the libraries in the application after doing a new ES build.

On Mon, Jul 12, 2010 at 12:08 PM, Samuel Doyle samueldoyle@gmail.comwrote:

Hi, I just updated today and now I'm seeing the following exception in ES
on startup.

[12:02:30,876][WARN ][discovery.zen.publish ] [Zip-Zap] failed to send
cluster state to [[Agent
Zero][bd671b76-eb40-4481-87b2-c9a479f5cc1f][inet[/192.168.22.131:9301]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...
org.elasticsearch.transport.RemoteTransportException: [Agent
Zero][inet[/192.168.22.131:9301]][discovery/zen/publish]
Caused by: java.lang.IndexOutOfBoundsException
at
org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:52)
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:100)
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:70)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readBlockSet(ClusterBlocks.java:265)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readClusterBlocks(ClusterBlocks.java:233)
at
org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:220)
at
org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequest.readFrom(PublishClusterStateAction.java:90)
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:170)
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:80)
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.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
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:51)
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:281)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

kimchy · July 12, 2010, 7:43pm

Yea, currently, it is needed. I will work on backward comp. once ES will
mature more (no need to support backward comp. now helps me move much
faster).

-shay.banon

On Mon, Jul 12, 2010 at 10:17 PM, Samuel Doyle samueldoyle@gmail.comwrote:

Hi, sorry this is a false alarm, must make a mental note to always update
the libraries in the application after doing a new ES build.

On Mon, Jul 12, 2010 at 12:08 PM, Samuel Doyle samueldoyle@gmail.comwrote:

Hi, I just updated today and now I'm seeing the following exception in ES
on startup.

[12:02:30,876][WARN ][discovery.zen.publish ] [Zip-Zap] failed to send
cluster state to [[Agent
Zero][bd671b76-eb40-4481-87b2-c9a479f5cc1f][inet[/192.168.22.131:9301]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...
org.elasticsearch.transport.RemoteTransportException: [Agent
Zero][inet[/192.168.22.131:9301]][discovery/zen/publish]
Caused by: java.lang.IndexOutOfBoundsException
at
org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:52)
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:100)
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:70)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readBlockSet(ClusterBlocks.java:265)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readClusterBlocks(ClusterBlocks.java:233)
at
org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:220)
at
org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequest.readFrom(PublishClusterStateAction.java:90)
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:170)
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:80)
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.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
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:51)
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:281)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

otisg · July 13, 2010, 4:31am

Shay,

This bit about not worrying about backwards compatibility might be
worth stating in some more visible place.
For example, for those of us using ES, it's important to know whether
with each ES upgrade we may have to reindex everything from scratch.
It would be great to document your intentions/plans/guarantees or lack
of them.

Thanks,
Otis

Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/

On Jul 12, 3:43 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Yea, currently, it is needed. I will work on backward comp. once ES will
mature more (no need to support backward comp. now helps me move much
faster).

-shay.banon

On Mon, Jul 12, 2010 at 10:17 PM, Samuel Doyle samueldo...@gmail.comwrote:

Hi, sorry this is a false alarm, must make a mental note to always update
the libraries in the application after doing a new ES build.

On Mon, Jul 12, 2010 at 12:08 PM, Samuel Doyle samueldo...@gmail.comwrote:

Hi, I just updated today and now I'm seeing the following exception in ES
on startup.

[12:02:30,876][WARN ][discovery.zen.publish ] [Zip-Zap] failed to send
cluster state to [[Agent
Zero][bd671b76-eb40-4481-87b2-c9a479f5cc1f][inet[/192.168.22.131:9301]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...
org.elasticsearch.transport.RemoteTransportException: [Agent
Zero][inet[/192.168.22.131:9301]][discovery/zen/publish]
Caused by: java.lang.IndexOutOfBoundsException
at
org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:52)
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:100)
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:70)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readBlockSet(ClusterBlocks.java:265)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readClusterBlocks(ClusterBlocks.java:233)
at
org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:220)
at
org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequest.readFrom(PublishClusterStateAction.java:90)
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:170)
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:80)
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.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
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:51)
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:281)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

kimchy · July 13, 2010, 7:13am

You are right, I will add this info to the docs. The current state of ES is
that binary backward compatibility is not something that I enforce (for the
sake of moving forward as fast as possible). Reindexing is something that I
do try to minimize the need to, but at this state of elasticsearch, sadly,
it might be required when upgrading to a new version. Version 0.9, for
example, require reindexing because of the "reuse work dir" feature when
recovering from the gateway.

Those unknown unknowns are a bitch, and though they usually can be solved by
architecting your product to handle them, maintaing it is a pain which I
would like to avoid in the current state of ES.

-shay.banon

On Tue, Jul 13, 2010 at 7:31 AM, Otis otis.gospodnetic@gmail.com wrote:

Shay,

This bit about not worrying about backwards compatibility might be
worth stating in some more visible place.
For example, for those of us using ES, it's important to know whether
with each ES upgrade we may have to reindex everything from scratch.
It would be great to document your intentions/plans/guarantees or lack
of them.

Thanks,
Otis

Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/

On Jul 12, 3:43 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Yea, currently, it is needed. I will work on backward comp. once ES will
mature more (no need to support backward comp. now helps me move much
faster).

-shay.banon

On Mon, Jul 12, 2010 at 10:17 PM, Samuel Doyle <samueldo...@gmail.com
wrote:

Hi, sorry this is a false alarm, must make a mental note to always
update
the libraries in the application after doing a new ES build.

On Mon, Jul 12, 2010 at 12:08 PM, Samuel Doyle <samueldo...@gmail.com
wrote:

Hi, I just updated today and now I'm seeing the following exception in
ES
on startup.

[12:02:30,876][WARN ][discovery.zen.publish ] [Zip-Zap] failed to
send
cluster state to [[Agent
Zero][bd671b76-eb40-4481-87b2-c9a479f5cc1f][inet[/192.168.22.131:9301
]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...
org.elasticsearch.transport.RemoteTransportException: [Agent
Zero][inet[/192.168.22.131:9301]][discovery/zen/publish]
Caused by: java.lang.IndexOutOfBoundsException
at

org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:52)
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:100)
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:70)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readBlockSet(ClusterBlocks.java:265)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readClusterBlocks(ClusterBlocks.java:233)
at
org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:220)
at
org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequest.readFrom(PublishClusterStateAction.java:90)
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:170)
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:80)
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.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
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:51)
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:281)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Lukas_Vlcek1 · July 13, 2010, 7:34am

Hi,

There is an attempt to create release notes for 0.9.0 (Clinton did very nice
job on updating it). My understanding is that this document should be
included in the disto itself before the release is finished.
http://wiki.github.com/elasticsearch/elasticsearch/release-notes

Lukas

On Tue, Jul 13, 2010 at 9:13 AM, Shay Banon shay.banon@elasticsearch.comwrote:

You are right, I will add this info to the docs. The current state of ES is
that binary backward compatibility is not something that I enforce (for the
sake of moving forward as fast as possible). Reindexing is something that I
do try to minimize the need to, but at this state of elasticsearch, sadly,
it might be required when upgrading to a new version. Version 0.9, for
example, require reindexing because of the "reuse work dir" feature when
recovering from the gateway.

Those unknown unknowns are a bitch, and though they usually can be solved
by architecting your product to handle them, maintaing it is a pain which I
would like to avoid in the current state of ES.

-shay.banon

On Tue, Jul 13, 2010 at 7:31 AM, Otis otis.gospodnetic@gmail.com wrote:
Shay,

This bit about not worrying about backwards compatibility might be
worth stating in some more visible place.
For example, for those of us using ES, it's important to know whether
with each ES upgrade we may have to reindex everything from scratch.
It would be great to document your intentions/plans/guarantees or lack
of them.

Thanks,
Otis

Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/

On Jul 12, 3:43 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Yea, currently, it is needed. I will work on backward comp. once ES will
mature more (no need to support backward comp. now helps me move much
faster).

-shay.banon

On Mon, Jul 12, 2010 at 10:17 PM, Samuel Doyle <samueldo...@gmail.com
wrote:

Hi, sorry this is a false alarm, must make a mental note to always
update
the libraries in the application after doing a new ES build.

On Mon, Jul 12, 2010 at 12:08 PM, Samuel Doyle <samueldo...@gmail.com
wrote:

Hi, I just updated today and now I'm seeing the following exception
in ES
on startup.

[12:02:30,876][WARN ][discovery.zen.publish ] [Zip-Zap] failed to
send
cluster state to [[Agent
Zero][bd671b76-eb40-4481-87b2-c9a479f5cc1f][inet[/192.168.22.131:9301
]]{client=true,
data=false, zen.master=false}], should be detected as failed soon...
org.elasticsearch.transport.RemoteTransportException: [Agent
Zero][inet[/192.168.22.131:9301]][discovery/zen/publish]
Caused by: java.lang.IndexOutOfBoundsException
at

org.elasticsearch.common.netty.buffer.AbstractChannelBuffer.readByte(AbstractChannelBuffer.java:236)
at
org.elasticsearch.transport.netty.ChannelBufferStreamInput.readByte(ChannelBufferStreamInput.java:52)
at
org.elasticsearch.common.io.stream.HandlesStreamInput.readByte(HandlesStreamInput.java:100)
at
org.elasticsearch.common.io.stream.StreamInput.readVInt(StreamInput.java:70)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readBlockSet(ClusterBlocks.java:265)
at
org.elasticsearch.cluster.block.ClusterBlocks$Builder.readClusterBlocks(ClusterBlocks.java:233)
at
org.elasticsearch.cluster.ClusterState$Builder.readFrom(ClusterState.java:220)
at
org.elasticsearch.discovery.zen.publish.PublishClusterStateAction$PublishClusterStateRequest.readFrom(PublishClusterStateAction.java:90)
at
org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:170)
at
org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:80)
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.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)
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:51)
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:281)
at
org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at
org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Topic		Replies	Views
NodeNotConnectedException Elasticsearch	1	441	July 6, 2017
Remote Transport Exception in 5.1.1 w/JDK 1.8.0_111 Elasticsearch	21	5528	January 18, 2017
ES 7.4.0: Getting Exception when reading remote cluster stats Elasticsearch	2	463	November 14, 2019
Elasticsearch returns exception master not discovered Elasticsearch	1	777	July 20, 2017
Exceptions related admin cluster stats Elasticsearch	2	363	July 6, 2017

Seeing new exception in latest master

Thanks, Otis

Thanks, Otis

Thanks, Otis

Related topics

Thanks,
Otis

Thanks,
Otis

Thanks,
Otis