-
Couldn't load subscription status.
- Fork 96
Description
Context & versions
It seems that you can get the hydra-node stuck at ReplayingState. We've seen this happen when the state file is around 1gb; but haven't been able to consistently reproduce.
Steps to reproduce
Roughly:
- Have 5 parties
- Send lots of Txns
- Get a 1gb state file
- Stop the node
- Restart it
Actual behavior
It stalls at ReplayingState.
Expected behavior
It should continue fine, OR, it should crash with a reason for a deadlock.
Trivia
This is very related to this issue - #2086. Indeed, we could get the deadlock exception presented there by adding a link in the logging.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done ✔