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
All nodes were stuck at 85400, except for Demox which was stuck at 85398 and ANF node 4, which was stuck at 84348 due to a crash caused by reasons unknown (potentially high number of IO intensive block requests to the API). High API latency observed, up to almost a minute.
Initial Findings:
Lots of unconfirmed transmissions in bursts.
Recovery requires all nodes to shutdown (or at least a sufficient number of nodes including exclusion of the nodes that haven’t been restarted yet)
Nodes can advance without quorum
Restarting a node can cause a ledger to jump back dozens or hundreds of blocks
Potential Optimizations:
Are we checking transactions as existing in the ledger before we gossip them?
Can block specific ips or should we fallback on firewalls?
Ledger should support get ranges
Steps to Reproduce
Currently investigating. This issue is to track progress.
Expected Behavior
Network continues and block production progresses.
Your Environment
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
All nodes were stuck at 85400, except for Demox which was stuck at 85398 and ANF node 4, which was stuck at 84348 due to a crash caused by reasons unknown (potentially high number of IO intensive block requests to the API). High API latency observed, up to almost a minute.
Initial Findings:
Potential Optimizations:
Steps to Reproduce
Currently investigating. This issue is to track progress.
Expected Behavior
Network continues and block production progresses.
Your Environment
The text was updated successfully, but these errors were encountered: