-
Notifications
You must be signed in to change notification settings - Fork 880
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
Analyse Inbound Disconnect Reasons Per Client #6945
Comments
we get Inbound UNKNOWN disconnects from besu and OpenEthereum eg OpenEthereum/v3.3.5-hbbft-0.9.3-unstable-6b34c53cb-20231028/x86_64-linux-gnu/rustc1.68.2 |
running a modified version of #6947 on a holesky node note this holesky node only has 2 peers (the 2 bootnodes)
|
updated #6947 to make the analysis easier ^^ |
disconnect reasons matched with client type - this is all disconnects (excluding mismatched network ID) on 6609-9x nodes (3 nodes) over about an hour https://docs.google.com/spreadsheets/d/1Bbu7YWwuwRJJ3KByfpnZsw_S1GNo4O9itM7a14GhACo/edit#gid=1710195989 |
Looking at 6609-90 which did not gain any peers via discovery over the last 9 hours
Inbound
Outbound
|
some interesting stats (again off 6609-90 which seems to be stuck with zero peers)
Fail to connect reasons 87432
|
I've restarted besu on 6609-90 and it has connected to the 2 bootnodes and discovery looks a bit more varied (normal?)
|
agree @Beanow - I'm actually working on a related fix right now that will help a lot to get rid of UNKOWN disconnects |
@macfarla I also wonder out loud about 2 things:
#6968 mainly refers to the PeerReputation, though I'm not well versed in the matter enough to know if - in aggregate - this could lead to cliques or local maximum kinds of issues. |
useful command to collect data on disconnect reasons by client name example output from running local mainnet node (latest main) with teku for ~45 min https://docs.google.com/spreadsheets/d/1ZqsoD-wIlxZjOW1RokS8Op50ZxjuyPYkuF4Yp3RDB4g/edit?usp=sharing |
calling this done for now |
Related to #6805
We log enode with disconnect reason and client details with enode.
Cross reference these logs and see if there's a pattern
The text was updated successfully, but these errors were encountered: