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
{{ message }}
This repository has been archived by the owner on Nov 15, 2019. It is now read-only.
Currently Crust will evict peers from bootstrap cache, if they are being unresponsive for too long (2 minutes). The problem with this approach is that peers might become active in some time, e.g. a minute if he's only rebooting the machine. So we will remove peer from cache that potentially could help us bootstrap to the p2p network in the future. In addition, this happens even if the cache has not reached its limit.
Solution
If the cache is not full and previously cached peer is not responsive, don't evict it from the cache.
Evict peer from the bootstrap cache only when cache is full (has 200 entries) and we find out about a new directly accessible peer which we'd like to cache.
So remove all the time based external reachability tests of cached peers.
The text was updated successfully, but these errors were encountered:
The problem
Currently Crust will evict peers from bootstrap cache, if they are being unresponsive for too long (2 minutes). The problem with this approach is that peers might become active in some time, e.g. a minute if he's only rebooting the machine. So we will remove peer from cache that potentially could help us bootstrap to the p2p network in the future. In addition, this happens even if the cache has not reached its limit.
Solution
The text was updated successfully, but these errors were encountered: