Jörg, Done, https://github.com/elasticsearch/elasticsearch/issues/4639
Today when I investigated this issue, and just do a query to the time stamp when the exceptions is happening, data were indexed though. The reason I query is that, we worry if there is no data index during that period exceptions are happening , thus data lost. Thank you. Jason On Tue, Jan 7, 2014 at 4:34 PM, joergpra...@gmail.com <joergpra...@gmail.com > wrote: > Yes, it looks like two nodes do not agree about an update action and a > version conflict is pinging between them, node1 and node4. > > Not sure if this happens while index recovery or while an update is > executed, but it is definitely worth raising an issue at the Elasticsearch > github to let the Elasticsearch core team have a look. It might be some > kind of a deadlock. > > Jörg > > -- > 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/CAKdsXoGKNB-1KXab4eWhDnKpe4szdPsidEWq2his2j%3DfPwU7Zw%40mail.gmail.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHO4itzoqWdujn713RK83ZZL4iGr19nY9nz34wbRtTKOSzcMNA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
