This message was deleted.
# helpdesk
s
This message was deleted.
a
cc @great-umbrella-58130
g
that’s a bit out of my expertise, but I’m not seeing that error in our codebase
are multiple participants trying to connect with the same participant name?
p
I ll ask dev team
Hi, multiple participants have different names in our app. I reproduced the issue load testing with 500x livekit-cli instances tasks: total=500x rooms and 5/5 pubs/subs per room with ~10m ramp up. It seems there's some overlaping in dynamic port allocation, Does this makes sense?
g
Interesting… I’ve never seen this issue before. But its possible we just haven’t tested the TURN component as thoroughly. We’ll have to look into this some more. (cc @dry-elephant-14928 in case you have a better sense for why this is happening)
d
@polite-printer-17791 Is this actually causing any client failures for you? It's possible this is happening only due to the frequent connection/disconnections between load tester clients
p
Hi, currently no customer impact. We are preparing for football matches that induce high demand in short time. The issue is hapening in peak load testing. I see new rooms beeing allocated to already congested nodes and that is something we seak to avoid. That may be a reason to see this error.
g
@polite-printer-17791 you may want to set up node selector limits