First, i would try the workaround mentioned in the article: disable the compression and see if fixes the issue.
On Tue, Nov 11, 2014 at 1:42 PM, Christoph Tavan <christoph.ta...@gmail.com> wrote: > I'm running 1.3.1. Thanks a lot for the hint. I will try to upgrade and let > you know. > > What is the recommended way of upgrading? One minor version at a time or can > I do a rolling upgrade to 1.3.5? > > Thanks! > Christoph > > Am Dienstag, 11. November 2014 19:38:55 UTC+1 schrieb Robert Muir: >> >> The error says "local checksum OK"... what version of elasticsearch >> are you running? >> >> If its before 1.3.2, please read this: >> http://www.elasticsearch.org/blog/elasticsearch-1-3-2-released/ >> >> >> On Wed, Sep 3, 2014 at 12:58 AM, David Kleiner <david....@gmail.com> >> wrote: >> > Greetings, >> > >> > I tried to overcome slowly recovering replica set, changed the number of >> > replicas on index to 0, then to 1, getting this exception: >> > >> > >> > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- >> > [2014-09-02 23:51:59,738][WARN ][indices.recovery ] [Salvador >> > Dali] >> > [...-2014.08.29][1] File corruption on recovery name [_40d_es090_0.pos], >> > length [11345418], checksum [ekoi4m], writtenBy [LUCENE_4_9] local >> > checksum >> > OK >> > org.apache.lucene.index.CorruptIndexException: checksum failed (hardware >> > problem?) : expected=ekoi4m actual=1pdwf09 (resource=name >> > [_40d_es090_0.pos], length [11345418], checksum [ekoi4m], writtenBy >> > [LUCENE_4_9]) >> > at >> > >> > org.elasticsearch.index.store.Store$VerifyingIndexOutput.readAndCompareChecksum(Store.java:684) >> > at >> > >> > org.elasticsearch.index.store.Store$VerifyingIndexOutput.writeBytes(Store.java:696) >> > at >> > >> > org.elasticsearch.indices.recovery.RecoveryTarget$FileChunkTransportRequestHandler.messageReceived(RecoveryTarget.java:589) >> > at >> > >> > org.elasticsearch.indices.recovery.RecoveryTarget$FileChunkTransportRequestHandler.messageReceived(RecoveryTarget.java:533) >> > at >> > >> > org.elasticsearch.transport.netty.MessageChannelHandler$RequestHandler.run(MessageChannelHandler.java:275) >> > 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) >> > >> > >> > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- >> > >> > Any pointers? >> > >> > >> > -- >> > 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. >> > To view this discussion on the web visit >> > >> > https://groups.google.com/d/msgid/elasticsearch/cba135a4-7838-4ad5-b56c-439823f7653b%40googlegroups.com. >> > 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/b9dfd69c-94ce-4e15-ac84-04b0034a5f2d%40googlegroups.com. > > 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/CAOdYfZUSmuC_pfKP4%3DgRz4URYD82tMRo-ax%3D6L__jm-804E2qQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
