clint,
I just tried adding a curl
-XGET 'http://localhost:9200/_cluster/health?wait_for_status=yellow'
(yellow because I only have 1 node in the test setup so no replicas) and
still get the same error. I'm going to try pulling the latest and see if it
still occurs with that version
Thanks for the help anyway!
Matt
On Mar 2, 2011 10:55am, purplegherkin@gmail.com wrote:
clint,
Thanks for the reply! I'm definitely getting an error on the final delete
everytime I try it (all the other command succeed as expected):
{"took":9,"items":[{"delete":{"_index":"err_test_real","_type":"results","_id":"8a08dfb3af854f07b72b04b977f27f2a:81","error":"VersionConflictEngineException[[err_test_real][4]
[results][8a08dfb3af854f07b72b04b977f27f2a:81]:
version conflict, current
[-1], required [2]]"}}]}
I suppose I could try the cluster_health check (I'll have to dig into how
that's done), but I was under the impression that doing a refresh on the
index waiting until everything was flushed out before it returns, which
is why that call is there before the delete (or am I incorrect on the
refresh use?)
On Mar 2, 2011 10:34am, Clinton Gormley clinton@iannounce.co.uk> wrote:
Hi Matt
I'm working with the latest build of ES (just downloaded yesterday
morning from source) and I've come across an issue where when I
attempt to do a bulk delete of a child document, I'm getting an error
saying versions don't match (even through I don't specify a version,
which I understood to mean use the latest). I put a curl example at
I've tried your script both on 0.15.1 and the latest from master (from
today).
I don't get any errors. All works fine.
But I wonder if adding a cluster_health 'wait_for_status' pause after
your refresh might help?
clint