Operation missing in history

[sschiessl-bcp]

In abits ES

[sschiessl-bcp]

In particular: 1.11.1184817920 and 1.11.1184759958 and 1.11.1184730270

Those ids are simply missing in the ES ... investigating

[sschiessl-bcp]

There are the current settings of the feeder

bitshares_es_latest_block: 64407291
blockchain_plugins:
 - elasticsearch
 - es_objects
blockchain_args: >
    --ignore-api-helper-indexes-warning
    --elasticsearch-start-es-after-block={{bitshares_es_latest_block}}
    --es-objects-start-es-after-block={{bitshares_es_latest_block}}
    --es-objects-keep-only-current=true
    --elasticsearch-operation-object=true
    --elasticsearch-operation-string=false

Running since 6 weeks on 6.0.0.

[sschiessl-bcp]

Are there cases that the ES plugin can fail on insert, but the core continues to next block @abitmore ? I remember that core gets stuck on the block if ES fails.

[abitmore]

bitshares/bitshares-core#2549 (comment)

[abitmore]

Are there cases that the ES plugin can fail on insert, but the core continues to next block @abitmore ? I remember that core gets stuck on the block if ES fails.

I found a bug in the elasticsearch plugin: bitshares/bitshares-core#2693

[abitmore]

In particular: 1.11.1184817920 and 1.11.1184759958 and 1.11.1184730270

Those ids are simply missing in the ES ... investigating

https://blocksights.info/#/blocks/65420034 does not load. It is the block containing 1.11.1184759958. See #26.

I think you need to do a full replay to fix these issues. A full replay will be needed anyway for the 6.1.0 release.

[abitmore]

It seems this issue is still there. I guess you haven't performed a full replay yet.