Open davidkellerman opened 6 years ago
Yeah, need to figure out what's generating these - I'm wondering if there's a duplicate update being sent, since docs and error would indicate this by itself won't do the update, but it does seem to be updated in ES.
More generally, we should be catching exceptions on update and really logging them at a minimum, rather than this unhandled noise.
Any steps to reproduce you can add, I've seen these but not currently able to cause it. Not sure what document index call would cause the _version
to actually be included in the doc sent to ES so maybe this is internally triggered by ... I don't know. ES docs suggest that version checking is only done if the version is sent in the update, and it's true I don't see version in what I'm sending that isn't causing this today...
When updating records, Elasticsearch generates "version conflict" errors. It seems to do the update, but the error messages really overwhelm the logging.