You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like now Indy Node/Plenum cannot successfully catch up when node is too much behinds (for example new node joining 3-years old pool with 10000s transactions). While workaround is possible (just copy data) it would be much better if node could catch up using normal process.
We've onboarded a number of Stewards onto the various Sovrin networks since this issue was reported. The new nodes do catch up and reach consensus, but it takes a few hours (3 or so) for this to occur (without seeding the node with an ledger data).
It looks like now Indy Node/Plenum cannot successfully catch up when node is too much behinds (for example new node joining 3-years old pool with 10000s transactions). While workaround is possible (just copy data) it would be much better if node could catch up using normal process.
More details (including logs with failed catch-up) can be found here: https://sovrin.atlassian.net/browse/SN-18
Acceptance criteria
The text was updated successfully, but these errors were encountered: