Skip to content
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

Detect and restart stuck nodes #1917

Open
DrZoltanFazekas opened this issue Nov 28, 2024 · 0 comments
Open

Detect and restart stuck nodes #1917

DrZoltanFazekas opened this issue Nov 28, 2024 · 0 comments
Assignees
Labels
Agate Required for mainnet launch

Comments

@DrZoltanFazekas
Copy link
Contributor

In case we can't fix the root causes for nodes getting stuck, we should provide a fully automated workaround e.g. a cron job that check every few minutes the block number returned by localhost:4201 and the block number returned by the load balancer and restarts the container if the node seems to be stuck while the network is progressing.

@DrZoltanFazekas DrZoltanFazekas added the Aventurine Required for proto-mainnet launch label Nov 28, 2024
@DrZoltanFazekas DrZoltanFazekas changed the title Detecting and restarting stuck nodes Detect and restart stuck nodes Nov 29, 2024
@DrZoltanFazekas DrZoltanFazekas added Agate Required for mainnet launch and removed Aventurine Required for proto-mainnet launch labels Dec 2, 2024
@shawn-zil shawn-zil self-assigned this Dec 11, 2024
@shawn-zil shawn-zil linked a pull request Dec 12, 2024 that will close this issue
@frankmeds frankmeds self-assigned this Dec 12, 2024
@shawn-zil shawn-zil removed their assignment Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agate Required for mainnet launch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants