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
Using WAN federation or cluster peer-to-peer, when the peer network is interrupted and unable to connect,
Consul's memory will continue to grow until OOM
Overview of the Issue
Using WAN federation or cluster peer-to-peer, when the peer network is interrupted and unable to connect,
Consul's memory will continue to grow until OOM
Reproduction Steps
4.dc02:
CPUS MEMS% VIRT RES PID USER Command('k' to kill)
11 93.0 59.6G 58.4G 266365 zwsx consul agent config-dir=consul.d/
...
Operating system and Environment details
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Log Fragments
many error log
1月 03 13:17:23 node92 consul[2755953]: 2025-01-03T13:17:23.202+0800 [WARN] agent: [core][Channel #21313 SubChannel #21314] grpc: addrConn.createTransport failed to connect to {Addr: "218.66*.:85>
1月 03 13:17:23 node92 consul[2755953]: 2025-01-03T13:17:23.202+0800 [ERROR] agent.server.peering-syncer: error managing peering stream: peer_id=0cdd8131-59ae-2206-1b19-717471ea320c peer_name=dc01 >
1月 03 13:17:23 node92 consul[2755953]: 2025-01-03T13:17:23.221+0800 [WARN] agent: [core][Channel #21315 SubChannel #21316] grpc: addrConn.createTransport failed to connect to {Addr: "218.66.:85>
1月 03 13:17:23 node92 consul[2755953]: 2025-01-03T13:17:23.221+0800 [ERROR] agent.server.peering-syncer: error managing peering stream: peer_id=0cdd8131-59ae-2206-1b19-717471ea320c peer_name=dc01 >
1月 03 13:17:23 node92 consul[2755953]: 2025-01-03T13:17:23.231+0800 [WARN] agent: [core][Channel #21317 SubChannel #21318] grpc: addrConn.createTransport failed to connect to {Addr: "218.66.*:85>
...
...
The text was updated successfully, but these errors were encountered: