We have two processes, each running on different machines that operate on an ES cluster. One process indexes a document using write consistency ALL and then makes the document available to the other process right away. The other process performs some other work and then it needs to set a flag in the document to make it searchable - this is done using the Update API. In 90-95% of the cases, this works fine but in some rare instances we are seeing 404s on the /_update request. Though even rarer (< 1%), we see a 409 response code. I would've thought that write consistency ALL would make the document available for the update API. Can anyone comment on this use case or why we might be seeing these issues (or if this is a known issue)? We're currently running 0.90.7 in the cluster and have 5 members that are data/master true.
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7de196d8-ee4e-4502-a326-c9831b32673d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
