The elasticsearch plugin does not send data in memory to ElasticSearch when the node is shutting down. If the node is still syncing (30+ seconds behind the current head block time), after it is restarted, it will resume from a potential much later block number.
Related:
If the node is already in sync, the elasticsearch plugin sends data to ElasticSearch on every block, so no issue.
The missing data can be fixed with a replay with an appropriate starting block number.
This issue does not exist in the es_objects plugin (version test-6.1.2).
Bug Description
The
elasticsearchplugin does not send data in memory to ElasticSearch when the node is shutting down. If the node is still syncing (30+ seconds behind the current head block time), after it is restarted, it will resume from a potential much later block number.Related:
elasticsearchplugin sends data to ElasticSearch on every block, so no issue.es_objectsplugin (versiontest-6.1.2).https://github.com/blocksights/blocksights-open-explorer/issues/7 might be caused by this issue.
This might be the answer to https://github.com/bitshares/bitshares-core/issues/2549#issuecomment-991921614
https://github.com/bitshares/bitshares-core/issues/2493 is also somewhat related.
Impacts Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.
Host Environment Please provide details about the host environment. Much of this information can be found running:
witness_node --version.test-6.1.2CORE TEAM TASK LIST