You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running a node on mainnet has shown that even though I have good connectivity (~60 peers), my node's peerTracker only contains 3 tracked peers. It's likely due to aggressive peer scoring. We may need to be more lenient with it as it's better to have more trackedPeers that may have "mid-level" scores instead of only keeping the absolute best (which may be a very small pool).
We need to consider the scoring mechanism and adjust accordingly. We can only start doing this once we have a dashboard for the metrics that have just been implemented so we can make an informed decision.
The text was updated successfully, but these errors were encountered:
We can add minAmount of peer to peer tracker. If amount of connect peers is less than minAmount it should not remove connected peers. It will solve original issue and should be quick to implement and give us time to select and implement smarter scoring arithmetic.
Running a node on mainnet has shown that even though I have good connectivity (~60 peers), my node's
peerTracker
only contains 3 tracked peers. It's likely due to aggressive peer scoring. We may need to be more lenient with it as it's better to have more trackedPeers that may have "mid-level" scores instead of only keeping the absolute best (which may be a very small pool).We need to consider the scoring mechanism and adjust accordingly. We can only start doing this once we have a dashboard for the metrics that have just been implemented so we can make an informed decision.
The text was updated successfully, but these errors were encountered: