> Can you post more information about the IndexCorruptedException, stacktrace,
> or reproduction?
>
I have to correct me: CorruptIndexException
[2014-11-21 20:15:44,225][WARN ][cluster.action.shard ] [isetta]
[XXXXX][2] received shard failed for [ips-mac-mips-mac-k01-2014.08][2],
node[KjJsJYd8TXShEgm1S25_Zw], [R], s[INITIALIZING], indexUUID
[onrMITrgRTyIDc4RL-p8xQ], reason [engine failure, message [corrupted
preexisting index][CorruptIndexException[[XXXXX][2] Preexisting corrupted
index [corrupted_aPP4lMokQsKstBqLfYTTTA] caused by:
CorruptIndexException[checksum failed (hardware problem?) : expected=uhifyc
actual=drw2lb (resource=name [_rgh_es090_0.pos], length [142663622],
checksum [uhifyc], writtenBy [4.10.2])]
org.apache.lucene.index.CorruptIndexException: checksum failed (hardware
problem?) : expected=uhifyc actual=drw2lb (resource=name
[_rgh_es090_0.pos], length [142663622], checksum [uhifyc], writtenBy
[4.10.2])
at
org.elasticsearch.index.store.Store$VerifyingIndexOutput.readAndCompareChecksum(Store.java:882)
at
org.elasticsearch.index.store.Store$VerifyingIndexOutput.writeBytes(Store.java:894)
at
org.elasticsearch.indices.recovery.RecoveryTarget$FileChunkTransportRequestHandler.messageReceived(RecoveryTarget.java:591)
at
org.elasticsearch.indices.recovery.RecoveryTarget$FileChunkTransportRequestHandler.messageReceived(RecoveryTarget.java:535)
at
org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.run(MessageChannelHandler.java:275)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
]]]
>
> Where did you get the information that 7u51 produces
> IndexCorruptedException?
>
Take a look at here: http://wiki.apache.org/lucene-java/JavaBugs
especially to https://issues.apache.org/jira/browse/LUCENE-5212
>
> Jörg
>
>
> On Tue, Nov 25, 2014 at 9:11 AM, <msbr...@gmail.com <javascript:>> wrote:
>
>> Some shards on my ES-Instance get an IndexCorruptedException. I assume
>> this was caused by java 1.7u51, which may cause such issues. But how to
>> recover from this corrupted shard? The currently affected shards seems
>> endless to be recovered and the ES-logs grow up to several megabytes of
>> size. I assume the data within tha affected shards is lost. But how to
>> delete the affected shards?
>>
>> regards,
>> markus
>>
>> --
>> 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 elasticsearc...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/9af4e6f5-509c-42fe-86c1-430170c0366b%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/9af4e6f5-509c-42fe-86c1-430170c0366b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/ae85a983-19af-4d49-8e32-88dc1c214289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
