-
Notifications
You must be signed in to change notification settings - Fork 30
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
delayed response from mainnet nodes #2
Comments
I'm sorry you're having a bad experience; you should get responses much faster.
|
Thanks a lot Luke for quick reply
|
Most likely the updater just hasn't had a chance to sync completely, so when the nodes launch, they also launch without being completely in sync, and after ~45 minutes of being out of sync/unhealthy, they will be terminated and replaced by new nodes. It can take weeks to sync from scratch. If you don't want to wait weeks for your updater to sync all the way from scratch, the best option is to copy the files from an existing S3 bucket maintained by the Tezos Foundation updaters. There are instructions for doing this here: https://assets.tqtezos.com/docs/run-a-node/4-tezos-updater/ under the section titled "Initiate the data copy," but you should first shut down your updater by updating the CloudFormation stack and setting desired tasks to 0 so that it doesn't try to overwrite those files while you are copying them. Once the files are copied, follow the next step "Update ECS tasks" to start your updater again. At that point, your node tasks should get the latest data from the updater and be able to start and get healthy/in sync in just a few minutes. |
I've deployed a node updater in my region after syncing data from s3 bucket of other region as mentioned in documentation. |
Total size for node1/node2 is 77.6GB for mainnet-updater bucket. |
Hi, so sorry about the problems you are having. I figured out what is happening. A few months ago, we switched from So, what is happening is that your updater and nodes are never able to properly sync data from other nodes. I just merged 2 PRs that will fix this, if you please merge them into your repositories, this should fix things and your updater will be able to sync fully to chain tip. It may take several hours for the updater to fully sync, since the data you have is behind several days, however, if you wanted to copy the S3 data again this will take less time. The most important changes are here: https://github.com/tqtezos/tezos-updater/blob/testnet/start-updater.sh#L13 and here: https://github.com/tqtezos/node-docker/blob/testnet/start-tezos.sh#L12 If you just add that line |
Thanks a lot luke for quick help. |
I've deployed AWS cloudforamtion setup following https://assets.tqtezos.com/docs/run-a-node/1-run-a-node-intro/ for mainnet.
The setup is successful but I'm facing issues with it.
The text was updated successfully, but these errors were encountered: