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
When a publisher's multiaddress changes, the new address(es) are added to the peerstore, and the old ones are left alone. Normally, the old addresses would expire after some time. If the polling period is within the temporary address TTL or there are frequent manual syncs, then this can keep resetting the old address expiration and prevent it from expiring.
The old addresses should be removed from the peerstore and only current/new addresses should be kept.
The text was updated successfully, but these errors were encountered:
Remove unused addrs from peerstore to prevent addresses that are no longer valid from continuing to be used.
Fixes#127
Update non-critical log messages to log at debug level.
Remove unused addrs from peerstore to prevent addresses that are no longer valid from continuing to be used.
Fixes#127
Update non-critical log messages to log at debug level.
* Remove unused addrs from peerstore
Remove unused addrs from peerstore to prevent addresses that are no longer valid from continuing to be used.
Fixes#127
Update non-critical log messages to log at debug level.
* Fix log message
* Add test to check that old address is removed from peerstore
When a publisher's multiaddress changes, the new address(es) are added to the peerstore, and the old ones are left alone. Normally, the old addresses would expire after some time. If the polling period is within the temporary address TTL or there are frequent manual syncs, then this can keep resetting the old address expiration and prevent it from expiring.
The old addresses should be removed from the peerstore and only current/new addresses should be kept.
The text was updated successfully, but these errors were encountered: