A store node with sync enabled fails to archive the "missing" messages identified by the sync process, because their timestamps are too old.
Impact
The store sync nodes indicate that they are synced, because the waku sync storage is updated, but the messages are never inserted into the DB. StoreQueryRequests will return no results.
To reproduce
If you can reproduce the behavior, steps to reproduce:
Run 2 store nodes with their own DB backends, one with relay enabled
Send a few relay message to the node which has it enabled.
Wait for the other node to sync
See that messages that are older than 20s at the time of syncing are not archived
Expected behavior
It is expected for all messages identified by the store sync process to be required by the store node, should be archived. the timestamps of the messages are already filtered to be within the store-sync-range config
Screenshots/logs
No error logs are produced for this issue
nwaku version/commit hash
This was specifically seen on nwaku versions: v0.33.0-rc.0-13-gd8e6a5 and v0.33.0-44-gc5a825, but it would have been present since store sync was implemented.
Problem
A store node with sync enabled fails to archive the "missing" messages identified by the sync process, because their timestamps are too old.
Impact
The store sync nodes indicate that they are synced, because the waku sync storage is updated, but the messages are never inserted into the DB. StoreQueryRequests will return no results.
To reproduce
If you can reproduce the behavior, steps to reproduce:
Expected behavior
It is expected for all messages identified by the store sync process to be required by the store node, should be archived. the timestamps of the messages are already filtered to be within the
store-sync-rangeconfigScreenshots/logs
No error logs are produced for this issue
nwaku version/commit hash
This was specifically seen on nwaku versions: v0.33.0-rc.0-13-gd8e6a5 and v0.33.0-44-gc5a825, but it would have been present since store sync was implemented.