-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICE candidate exception when do loadtest #38
Comments
Looks like a normal error thrown when the media server is overloaded, which is a condition to stop the test. Was the media server not loaded? (100% CPU) Seeing the number of sessions, it would look like it. |
When the exception occurred, the OpenVidu host CPU(4 cores) never up to 100% (total percentage), even the kurento-media-s process never up to 100% (single core percentage) |
I tested again, you see it throw exception when processing LoadTestSession28.
CPU usage as below.
|
You could try using RETRY_MODE=true in case it is just a Kurento fluke, as the error indicates that it comes from the server-side (kurento) kicking out a user, although RETRY_MODE in old versions is very buggy |
Where to set RETRY_MODE=true please?
You can see the exception occurred when processing LoadTestSession14, 14 for one worker node, 28 for two worker nodes, is there any limitation for WebRTC client sessions on Kurento server? any idea? |
Hi Team,
When I do test with v2.1.0, there is an exception that will cause the testing finished, please help take a look, thanks.
{"event":"exception","connectionId":"con_M8VzX8NMJK","reason":"There was an unexpected error on the server-side processing an ICE candidate generated and sent by the client-side"}
loadtest-controller logs as below.
The text was updated successfully, but these errors were encountered: