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

CosmosFullNode: Detect height drift and take action #286

Closed
1 of 2 tasks
DavidNix opened this issue Apr 28, 2023 · 2 comments · Fixed by #314
Closed
1 of 2 tasks

CosmosFullNode: Detect height drift and take action #286

DavidNix opened this issue Apr 28, 2023 · 2 comments · Fixed by #314
Assignees

Comments

@DavidNix
Copy link
Contributor

DavidNix commented Apr 28, 2023

This is probably an extension of SelfHeal.

There are some chains (primarily Evmos) that do not properly report the comet /status of catching up. They report as if they are in sync, but they fall behind.

With some manual testing, deleting and restarting the pod seems to correct the issue, at least with Evmos. There could be other actions like increasing the outbound peers but that will come with extra egress costs.

I feel deleting the pod (and the controller will recreate it) is a good first pass.

Tasks

@DavidNix
Copy link
Contributor Author

I've also seen this occasionally with Injective and other chains, but Evmos is the largest offender.

@jonathanpberger
Copy link
Contributor

Is there a vrt angle here around testing drift?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants