Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to sync translog(1.5.2) #12120

Closed
287400117 opened this issue Jul 8, 2015 · 5 comments
Closed

failed to sync translog(1.5.2) #12120

287400117 opened this issue Jul 8, 2015 · 5 comments

Comments

@287400117
Copy link

[2015-07-08 16:00:53,447][WARN ][index.engine ] [ES48225] [apksigs2015][32] failed to sync translog
[2015-07-08 16:00:53,451][WARN ][indices.cluster ] [ES48225] [[apksigs2015][32]] marking and sending shard failed due to [failed recovery]
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: [apksigs2015][32] failed to recover shard
at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:290)
at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:112)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.index.translog.TranslogCorruptedException: translog corruption while reading from stream
at org.elasticsearch.index.translog.ChecksummedTranslogStream.read(ChecksummedTranslogStream.java:72)
at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:260)
... 4 more
Caused by: org.elasticsearch.ElasticsearchIllegalArgumentException: No type mapped for [0]
at org.elasticsearch.index.translog.Translog$Operation$Type.fromId(Translog.java:237)
at org.elasticsearch.index.translog.ChecksummedTranslogStream.read(ChecksummedTranslogStream.java:66)
... 5 more

@s1monw
Copy link
Contributor

s1monw commented Jul 8, 2015

this is fixed in the upcoming 2.0 this is unfortunately expected to see these kind of corruptions on 1.5

@s1monw s1monw closed this as completed Jul 8, 2015
@287400117
Copy link
Author

Now, how do I fix it

@kuduk
Copy link

kuduk commented Aug 7, 2015

I resolved a similar problem caused by out of disk space. But in my log there are also something like that:

[2015-08-07 08:16:36,817][WARN ][cluster.action.shard ] [Lady Octopus] [logstash-2015.08.04][3] received shard failed for [logstash-2015.08.04][3], node[mM2oHJ1ERzSknGsLlSbanQ], [P], s[INITIALIZING], indexUUID [_KQOGo3tQj6iRxYBkZk7TQ], reason [shard failure [failed recovery][IndexShardGatewayRecoveryException[[logstash-2015.08.04][3] failed to recover shard]; nested: TranslogCorruptedException[translog corruption while reading from stream]; nested: ElasticsearchIllegalArgumentException[No version type match [95]]; ]]

so I could delete corrupted indicies in /var/lib/elasticsearch/elasticsearch/nodes/0/indices

@287400117
Copy link
Author

I also solved the problem, By removing translog, But some data may be lost

@kuduk
Copy link

kuduk commented Aug 7, 2015

In my case i was lucky i deleted only indicies, my data stay on logstash :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants