IndexFormatException: ES?

Elastic Stack Elasticsearch
1

Hi Everyone,
hoping someone can help with the below exception. I've indexed a bunch
of data using ES, with the S3 gateway (I realize this is deprecated but it
has served us well).

I'm running ES (0.20.6) using elasticsearch-spring embedded in a war.
Problem is, after a restart, the service hangs on startup. Can anyone shed
any light on why this exception might be occurring?

18:15:20.217 [DEBUG] o.e.cluster.service - [Mary Walker] processing
[shard-failed ([dataset_metadata][3], node[lzJ-UcPdTvujT9CX0KDKQg], [P],
s[INITIALIZING]), reason [Failed to start shard, message
[IndexShardGatewayRecoveryException[[dataset_metadata][3] failed to recover
commit_point [commit-4]/[4]]; nested:
EngineCreationFailureException[[dataset_metadata][3] failed to create
engine]; nested: IndexFormatTooOldException[Format version is not supported
(resource:
ChecksumIndexInput(NIOFSIndexInput(path="/usr/share/tomcat7/data/mydata/nodes/0/indices/dataset_metadata/3/index/segments_1"))):
1071082519 (needs to be between -1 and -11). This version of Lucene only
supports indexes created with release 1.9 and later.]; ]]]: done applying
updated cluster_state

I tried upgrading ES versions, but no dice.

Thanks in advance,

--paul

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

2

Did another node with a different ES version opened the data directory? It
could be that the index index got corrupted. Are all the shards failing?

On 11 September 2013 20:34, Paul Sanwald paul@redowlanalytics.com wrote:

Hi Everyone,
hoping someone can help with the below exception. I've indexed a bunch
of data using ES, with the S3 gateway (I realize this is deprecated but it
has served us well).

I'm running ES (0.20.6) using elasticsearch-spring embedded in a war.
Problem is, after a restart, the service hangs on startup. Can anyone shed
any light on why this exception might be occurring?

18:15:20.217 [DEBUG] o.e.cluster.service - [Mary Walker] processing
[shard-failed ([dataset_metadata][3], node[lzJ-UcPdTvujT9CX0KDKQg], [P],
s[INITIALIZING]), reason [Failed to start shard, message
[IndexShardGatewayRecoveryException[[dataset_metadata][3] failed to recover
commit_point [commit-4]/[4]]; nested:
EngineCreationFailureException[[dataset_metadata][3] failed to create
engine]; nested: IndexFormatTooOldException[Format version is not supported
(resource:
ChecksumIndexInput(NIOFSIndexInput(path="/usr/share/tomcat7/data/mydata/nodes/0/indices/dataset_metadata/3/index/segments_1"))):
1071082519 (needs to be between -1 and -11). This version of Lucene only
supports indexes created with release 1.9 and later.]; ]]]: done applying
updated cluster_state

I tried upgrading ES versions, but no dice.

Thanks in advance,

--paul

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Met vriendelijke groet,

Martijn van Groningen

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

3

Martijn - thanks for the reply.

We figured this out late yesterday, this was an interesting one: The
problem was that the ec2 instance that was firing up elasticsearch is
(since I'm using the s3 gateway) loading data from S3 into its local
storage. This was taking a long time, and as a result, the application
context we were using was timing out the ES initialization before the load
could finish.

This resulted in a corrupt local index, which resulted in the above
exception. Hopefully this post will save someone some time at some point in
the future.

Next step for me: move off of S3 gateway, as it's deprecated!

--paul

On Thu, Sep 12, 2013 at 4:16 AM, Martijn v Groningen <
martijn.v.groningen@gmail.com> wrote:

Did another node with a different ES version opened the data directory? It
could be that the index index got corrupted. Are all the shards failing?

On 11 September 2013 20:34, Paul Sanwald paul@redowlanalytics.com wrote:

Hi Everyone,
hoping someone can help with the below exception. I've indexed a bunch
of data using ES, with the S3 gateway (I realize this is deprecated but it
has served us well).

I'm running ES (0.20.6) using elasticsearch-spring embedded in a war.
Problem is, after a restart, the service hangs on startup. Can anyone shed
any light on why this exception might be occurring?

18:15:20.217 [DEBUG] o.e.cluster.service - [Mary Walker] processing
[shard-failed ([dataset_metadata][3], node[lzJ-UcPdTvujT9CX0KDKQg], [P],
s[INITIALIZING]), reason [Failed to start shard, message
[IndexShardGatewayRecoveryException[[dataset_metadata][3] failed to recover
commit_point [commit-4]/[4]]; nested:
EngineCreationFailureException[[dataset_metadata][3] failed to create
engine]; nested: IndexFormatTooOldException[Format version is not supported
(resource:
ChecksumIndexInput(NIOFSIndexInput(path="/usr/share/tomcat7/data/mydata/nodes/0/indices/dataset_metadata/3/index/segments_1"))):
1071082519 (needs to be between -1 and -11). This version of Lucene only
supports indexes created with release 1.9 and later.]; ]]]: done applying
updated cluster_state

I tried upgrading ES versions, but no dice.

Thanks in advance,

--paul

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Met vriendelijke groet,

Martijn van Groningen

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/cwD-OIrXpHM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.