[Elasticsearch Sink, cip25-assets] Error on restarting oura

[mesudip]

I am tring to index cip25 assets using aura to elasticsearch v8.3.3. Container was once restarted and now container stops everytime with Document Already Exists error.

In case of elasticsearch sink It would be nice to ignore error if message is "Document already exists".

Container log

[2022-08-02T17:22:55Z INFO  oura::sources::n2n::run] rolling forward to point (61859075, a8df803109469af05c6d1be595134a1504da6dd1411a0a7786e9d121354acb4e)
[2022-08-02T17:22:55Z INFO  oura::sources::n2n::run] rollback buffer state, size: 0, oldest: None, latest: None
[2022-08-02T17:22:55Z ERROR oura::sinks::elastic::run] error indexing record in Elasticsearch: error pushing event to elastic: Ok("{\"error\":{\"root_cause\":[{\"type\":\"version_conflict_engine_exception\",\"reason\":\"[61858889.cip25.156334089489442901343902397614543635674]: version conflict, document already exists (current version [1])\",\"index_uuid\":\"_AlljuaPRnq7UbOiGILYug\",\"shard\":\"0\",\"index\":\".ds-oura.sink.cip25assets.mainnet-2022.07.29-000001\"}],\"type\":\"version_conflict_engine_exception\",\"reason\":\"[61858889.cip25.156334089489442901343902397614543635674]: version conflict, document already exists (current version [1])\",\"index_uuid\":\"_AlljuaPRnq7UbOiGILYug\",\"shard\":\"0\",\"index\":\".ds-oura.sink.cip25assets.mainnet-2022.07.29-000001\"},\"status\":409}")
[2022-08-02T17:22:55Z INFO  oura::sources::n2n::run] rolling forward to point (61859085, 5d6e02f5ca04f196abd85b568250b94eef0d61ab646706e5ae1f996054e406f5)
[2022-08-02T17:22:55Z INFO  oura::sources::n2n::run] rollback buffer state, size: 0, oldest: None, latest: None
thread '<unnamed>' panicked at 'writer loop failed: "error pushing event to elastic: Ok(\"{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"version_conflict_engine_exception\\\",\\\"reason\\\":\\\"[61858889.cip25.156334089489442901343902397614543635674]: version conflict, document already exists (current version [1])\\\",\\\"index_uuid\\\":\\\"_AlljuaPRnq7UbOiGILYug\\\",\\\"shard\\\":\\\"0\\\",\\\"index\\\":\\\".ds-oura.sink.cip25assets.mainnet-2022.07.29-000001\\\"}],\\\"type\\\":\\\"version_conflict_engine_exception\\\",\\\"reason\\\":\\\"[61858889.cip25.156334089489442901343902397614543635674]: version conflict, document already exists (current version [1])\\\",\\\"index_uuid\\\":\\\"_AlljuaPRnq7UbOiGILYug\\\",\\\"shard\\\":\\\"0\\\",\\\"index\\\":\\\".ds-oura.sink.cip25assets.mainnet-2022.07.29-000001\\\"},\\\"status\\\":409}\")"', src/sinks/elastic/setup.rs:62:67
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at 'error sending filter message: SendError { .. }', src/filters/selection.rs:111:43
thread '<unnamed>' panicked at 'error sending filter message: SendError { .. }', src/filters/fingerprint.rs:268:37

[scarmuega]

@mesudip thanks for reporting!

I've managed to replicate. This isn't the expected behavior. I'll work on a hotfix for version 1.5.