ExaBGP v4.2.22 hangs / does not announce routes after stress

[Sai Kiran G]

Hi exabgp-users!

I am using ExaBGP in my test environment between FRR and Arista EOS to announce and withdraw routes between the two. I have a test that is used to stress test our device. I see that when I try to stress test the environment by announcing and withdrawing lots of routes repeatedly ExaBGP instance running a process API is becoming unresponsive. I am not sure how I can troubleshoot the issue.

I have enabled exabgp debug logs but I don't see any error or failure messages there. Last few lines before it gives up look like this -

Thu, 30 Jan 2025 06:57:23 390    api           route removed from neighbor 10.10.246.32 local-ip 10.10.246.254 local-as 64600 peer-as 64600 router-id 10.10.246.254 family-allowed in-open : 193.11.248.0/25 next-hop 10.10.246.254 as-path [ 65534 64799 65515 ]
Thu, 30 Jan 2025 06:57:23 390    process       responding to http-api : done
Thu, 30 Jan 2025 06:57:23 390    configuration . route            | '193.11.248.128/25' 'next-hop' '10.10.246.254' 'as-path' '[' '65534' '64799' '65515' ']'
Thu, 30 Jan 2025 06:57:23 390    api           route removed from neighbor 10.10.246.32 local-ip 10.10.246.254 local-as 64600 peer-as 64600 router-id 10.10.246.254 family-allowed in-open : 193.11.248.128/25 next-hop 10.10.246.254 as-path [ 65534 64799 65515 ]
Thu, 30 Jan 2025 06:57:23 390    process       responding to http-api : done
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B A000 19C1 0BA0 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B A800 19C1 0BA8 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B B000 19C1 0BB0 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B B800 19C1 0BB8 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B C000 19C1 0BC0 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B C800 19C1 0BC8 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B D000 19C1 0BD0 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B D800 19C1 0BD8 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B E000 19C1 0BE0 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B E800 19C1 0BE8 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B F000 19C1 0BF0 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    sending TCP payload (  33) FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0021 0200 0A19 C10B F800 19C1 0BF8 8000 00
Thu, 30 Jan 2025 06:57:23 390    outgoing-1    >> 12 UPDATE(s)
Thu, 30 Jan 2025 06:57:23 390    ka-outgoing-1 receive-timer 172 second(s) left
Thu, 30 Jan 2025 06:57:23 390    ka-outgoing-1 send-timer 52 second(s) left
Thu, 30 Jan 2025 06:57:24 390    ka-outgoing-1 receive-timer 171 second(s) left
Thu, 30 Jan 2025 06:57:24 390    ka-outgoing-1 send-timer 51 second(s) left
Thu, 30 Jan 2025 06:57:26 390    ka-outgoing-1 receive-timer 170 second(s) left
Thu, 30 Jan 2025 06:57:26 390    ka-outgoing-1 send-timer 50 second(s) left

Any suggestions on what to look for in the log that may indicate an error with the API or ExaBGP would be very helpful!

Thank you

Regards

Sai 

[Thomas Mangin]

Please look how to convert version 3 api calls to version 4 on the wiki or disable the api ack feature.