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
We are running selenium grid in distributed mode on a docker swarm with 1 manager (8GB, 4CPUs), 2 workers (16GB, 8CPUs) and 2 workers (8GB, 4CPUs). We deployed the router, distributor, session-map and queue and event bus on the manager while on the 4 workers we deployed 45 nodes (15 for firefox, edge, chrome each).
Bug description
We usually run large test suites overnight and ever since the switch to grid 4 we've been facing huge performance issues first using hub and node, the hub often goes down due to oom error, we also tried distributed mode on a single vm (16GB, 8CPUs) and similarily the router goes down frequently, hence we moved the grid to a docker swarm just to slightly alleviate the huge memory consumption. We haven't deployed the current docker swarm to production yet so it's still functioning fairly well but from cadvisor metrics we see that the router keeps accumulating memory without releasing it even when there are no tests, so it high likely we will face the same issue eventually
2022-10-06 12:06:59,260 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-router.conf" during parsing
2022-10-06 12:06:59,265 INFO RPC interface 'supervisor' initialized
2022-10-06 12:06:59,265 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-10-06 12:06:59,266 INFO supervisord started with pid 8
2022-10-06 12:07:00,268 INFO spawned: 'selenium-grid-router' with pid 10
Starting Selenium Grid Router...
2022-10-06 12:07:00,279 INFO success: selenium-grid-router entered RUNNING state, process has stayed up for> than 0 seconds (startsecs)
12:07:00.836 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
12:07:00.847 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
12:07:02.182 INFO [RouterServer.execute] - Started Selenium Router 4.5.0 (revision fe167b119a): http://10.0.0.84:4444
Operating System
RHEL 7.6; Docker version 18.03.0-ce, build 0520e24
Docker Selenium version (tag)
4.5.0-20221004
The text was updated successfully, but these errors were encountered:
What happened?
Context
We are running selenium grid in distributed mode on a docker swarm with 1 manager (8GB, 4CPUs), 2 workers (16GB, 8CPUs) and 2 workers (8GB, 4CPUs). We deployed the router, distributor, session-map and queue and event bus on the manager while on the 4 workers we deployed 45 nodes (15 for firefox, edge, chrome each).
Bug description
We usually run large test suites overnight and ever since the switch to grid 4 we've been facing huge performance issues first using hub and node, the hub often goes down due to oom error, we also tried distributed mode on a single vm (16GB, 8CPUs) and similarily the router goes down frequently, hence we moved the grid to a docker swarm just to slightly alleviate the huge memory consumption. We haven't deployed the current docker swarm to production yet so it's still functioning fairly well but from cadvisor metrics we see that the router keeps accumulating memory without releasing it even when there are no tests, so it high likely we will face the same issue eventually
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
RHEL 7.6; Docker version 18.03.0-ce, build 0520e24
Docker Selenium version (tag)
4.5.0-20221004
The text was updated successfully, but these errors were encountered: