-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream Sync deployment TODO items #4139
Comments
Found one potential bug that will potentially effect the testnet downloader sync issue. After the fix, explorer node can finish the sync process without much delay. Further impact need to be observed. |
After deploying the fix #4150 to internal shard 3 explorer node, the node hasn't gone out of sync for the latest 48 hours, which mean the fix did resolve the issue on Testnet Explorer node. There are still some sync stuck issue which requires a node restart according to testnet test result. The stuck on validator nodes does not happen regularly. So I added more logs in downloader sync process to better observe the root cause of testnet validator fall out of sync: #4153. The fix would better be deployed to testnet nodes to give us a better understanding when the stuck happens again on validator node. |
The code has been run smoothly in testnet (No more out of sync issue) for the past few days. It would be sufficient for us to move the deployment to the next stage. - To deploy the code to mainnet node with probe nodes. It shall works as follows:
|
@PkayJava after discussion with @JackyWYX
All nodes should be in watchdog/grafana for easier monitoring. Make sure to choose s0 node all in different DC |
1. Overview
The document contains the steps taken to deploy the stream sync protocol.
2. Items and progress
The text was updated successfully, but these errors were encountered: