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
After a hold timer expires for a peer, GoBGP does not consider a peer to be down. In the following log, I expect to see Peer Down after 2024-04-24T17:37:12.600Z, but there isn't one.
GoBGP then starts accumulating outgoing BGP messages in the peer's message queue, until it eventually runs out of memory and crashes. I have verified by extending a gRPC API endpoint to expose the length of the queue for each peer's FSM, and periodically calling it.
The text was updated successfully, but these errors were encountered:
Version
GoBGP v2.10.0
Description
After a hold timer expires for a peer, GoBGP does not consider a peer to be down. In the following log, I expect to see
Peer Down
after2024-04-24T17:37:12.600Z
, but there isn't one.GoBGP then starts accumulating outgoing BGP messages in the peer's message queue, until it eventually runs out of memory and crashes. I have verified by extending a gRPC API endpoint to expose the length of the queue for each peer's FSM, and periodically calling it.
The text was updated successfully, but these errors were encountered: