ChainSafe / ChainSafe/gossamer
devnet "peer doesn't exist" error on node restart
- Dominant language
- Go
- Stars
- 454
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
## Task summary
- on a 3-node devnet, if you stop and restart one of the nodes, there will be a lot of peerset errors saying "peer doesn't exist":
```
2022-01-12T17:13:37Z EROR failed to do action {call=reportPeer, set-id=0, reputation change {-4 Duplicate gossip}, peers=[12D3KooWBzfWprE12qsJSr2nMKtfy4iGbXa75EiESufJ3sTwDAX5] on peerSet: peer doesn't exist peerset.go:L722 pkg=peerset
2022-01-12T17:13:38Z EROR failed to do action {call=reportPeer, set-id=0, reputation change {-4 Duplicate gossip}, peers=[12D3KooWBzfWprE12qsJSr2nMKtfy4iGbXa75EiESufJ3sTwDAX5] on peerSet: peer doesn't exist peerset.go:L722 pkg=peerset
2022-01-12T17:13:38Z EROR failed to do action {call=reportPeer, set-id=0, reputation change {-4 Duplicate gossip}, peers=[12D3KooWBzfWprE12qsJSr2nMKtfy4iGbXa75EiESufJ3sTwDAX5] on peerSet: peer doesn't exist peerset.go:L722 pkg=peerset
```
this shouldn't be happening, figure out why and fix it.
Contributor guide
Assessment
This issue has not been assessed yet.