rewind_single_block causes node to become unresponsive #21
Labels
Grin-Node
Test cases for GRIN-Node
ready-for-test
Ready to be assigned and be worked on
Test-Case
New test case
Some causes of rewind_single_block were fixed before 5.0.beta2 but the issue remains.
Issue: The node enters a loop of "rewind_single_block" and becomes unresponsive to API and fails to sync new blocks.
Testcase:
Start with an archive node
Call the nodes "get_block" API to fetch each block from 0 to tip.
Observe the node logs for message like
20201213 16:47:41.127 WARN grin_chain::txhashset::txhashset - rewind_single_block: 3 output_pos entries missing for: 000251721c7d at 781244
Expected Result:
no api timeouts
node should not fall behind in sync
Actual Results:
Observe that the node gives api timeouts while that rewind event is happening
Observe that immediately after the rewind event concludes the node reports being out of sync:
Some additional information
While the node is unresponsive:
It appears that this is the thread and stack trace for the event:
The text was updated successfully, but these errors were encountered: