-
Notifications
You must be signed in to change notification settings - Fork 251
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
use nim-websock
instead of news
#4061
Conversation
`news` has a few open issues that are not present in `nim-websock`: 1. There is a 1 second delay between each MB of sent data. 2. Cancelling an ongoing `send` makes the entire WebSocket unusable. 3. Control packets do not have priority over ongoing message frames. Using `news`, there are quite a few of these messages in Geth: ``` Previously seen beacon client is offline. Please ensure it is operational to follow the chain! ``` It may take quite some time to reconnect when this happens. Using `nim-websock`, this message still occurs because `eth1_monitor` reconnects the EL connection when no new blocks occurred for 5 minutes, but reconnecting is quick and the message is rarer.
Manual Notably, there was not a single logged |
Manual Goerli tests around head:
Will run it for longer to better understand the nature of those reconnects. |
There was a single disconnect now, due to one block being received too early, and then failing to obtain it for 5 minutes. During this, Geth did not make progress for 5 minutes, so Block
|
|
Prolonged |
news
has a few open issues that are not present innim-websock
:send
makes the entire WebSocket unusable.Using
news
, there are quite a few of these messages in Geth:It may take quite some time to reconnect when this happens.
Using
nim-websock
, this message still occurs becauseeth1_monitor
reconnects the EL connection when no new blocks occurred for 5 minutes,
but reconnecting is quick and the message is rarer.