Bug #25707
open
Ansible commands are slow to run through Foreman
Description
running remote command via Ansible on 48k hosts causes load almost 300
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1659037
Running remote command via Ansible on 48k hosts causes load almost 300
Steps to Reproduce:
1. Have 48k registered hosts with ReX ssh keys deployed
2. In the evening start this remote command:
subscription-manager refresh
yum repolist
yum -y install katello-host-tools
katello-package-upload --force
3. Check how is it going 9 hours later
Actual results:
After 4 hours, Satellite started swapping and used almost full swap. At maximum, it had a load of 296.
I have `killall ansible-playbook` (about 1200 of these was running), then `systemctl stop dynflowd` and `systemctl stop smart_proxy_dynflow_core`.
Updated by Adam Ruzicka over 5 years ago
- Project changed from Foreman Remote Execution to Ansible
- Subject changed from running remote command via Ansible on 48k hosts causes load almost 300 to running remote command via Ansible on 48k hosts causes load almost 300
To fix this we probably need to run a single ansible-playbook process for a group of hosts instead of running a process per host
Updated by Adam Ruzicka almost 5 years ago
This should improve dramatically now that we have support for ansible-runner
Updated by Ondřej Ezr almost 3 years ago
- Subject changed from running remote command via Ansible on 48k hosts causes load almost 300 to Ansible commands are slow to run through Foreman
- Description updated (diff)
- Triaged changed from No to Yes