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

zetaclient scheduler becomes desynced #3227

Open
gartnera opened this issue Nov 27, 2024 · 0 comments · May be fixed by #3228
Open

zetaclient scheduler becomes desynced #3227

gartnera opened this issue Nov 27, 2024 · 0 comments · May be fixed by #3228
Assignees
Labels
bug Something isn't working zetaclient Issues related to ZetaClient

Comments

@gartnera
Copy link
Member

gartnera commented Nov 27, 2024

It seems that TryOutboundProcessor will be called at different times on different machines (~5 seconds difference). This will degrade keysign performance.

image

This can partially be attributed desync based on the start time of zetaclient:

observeTicker := time.NewTicker(3 * time.Second)

We should subscribe to new block events via websockets like this so that we can react to new block immediately without polling.

@gartnera gartnera added the bug Something isn't working label Nov 27, 2024
@gartnera gartnera self-assigned this Nov 27, 2024
@gartnera gartnera added the zetaclient Issues related to ZetaClient label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working zetaclient Issues related to ZetaClient
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant