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

[vc] Investigate late attestations published on mainnet #4881

Closed
twoeths opened this issue Dec 7, 2022 · 5 comments
Closed

[vc] Investigate late attestations published on mainnet #4881

twoeths opened this issue Dec 7, 2022 · 5 comments
Assignees

Comments

@twoeths
Copy link
Contributor

twoeths commented Dec 7, 2022

Describe the bug

  • This is about the time we publish attestations compared to 1/3 of slot (so -2 means 1s after slot, +2 means 6s after slot
  • On goerli it rarely happens

Screen Shot 2022-12-07 at 16 00 48

  • However some mainnet nodes (v1.2.x) experienced this issue more

Screen Shot 2022-12-07 at 16 00 27

Expected behavior

Attestations should be published not later than 1/3 of slots

@twoeths twoeths self-assigned this Dec 7, 2022
@twoeths
Copy link
Contributor Author

twoeths commented Dec 7, 2022

This is because produceAttestationData being called after 4s (when vc hasn't received new chain head on time)

Screen Shot 2022-12-07 at 19 32 37

and produceAttestationData request time sometimes take >1s or even 5s

Screen Shot 2022-12-07 at 19 34 21

root cause is the I/O lag issue

@twoeths
Copy link
Contributor Author

twoeths commented Dec 8, 2022

We could try http 1.1 keep-alive (or http 2, that's a longer plan) to reuse http connection

@philknows
Copy link
Member

This is because produceAttestationData being called after 4s (when vc hasn't received new chain head on time)

Screen Shot 2022-12-07 at 19 32 37

and produceAttestationData request time sometimes take >1s or even 5s

Screen Shot 2022-12-07 at 19 34 21

root cause is the I/O lag issue

Referencing #4002

@twoeths
Copy link
Contributor Author

twoeths commented Dec 23, 2022

I've tried http 1.1 keep-alive, it does not help while v1.3.0 shows some improvement, see #4915 (comment)

@dapplion
Copy link
Contributor

Closing issues for specific incidents on old versions of Lodestar, please re-open if it happens with latest stable

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

No branches or pull requests

3 participants