-
Notifications
You must be signed in to change notification settings - Fork 199
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
mitogen 0.3.3 + ansible 2.12.8+: Broker has exitted #967
Comments
facing the same issue, Wating for the fixes. |
Experiencing the same issues. Commenting out the line as per the comment here seemed to fix. |
With 0af2ce8 this The error is slightly different, though:
Unfortunately, the only way I'm aware of to mitigate this is to downgrade to ansible 2.12.7. |
Found the issue. |
This workaround did not work for me, when running on 50+ hosts the playbook just "freeze" , revert to ansible 2.12.7 also did not work at the moment, I have to pursue investigations |
I'm not sure about all details here, but ansible-mitogen uses CPU pinning onto first two CPUs (you can see it when you run ansible with mitogen_linear with big number of hosts and forks, only first two CPUs are 100% busy). The more hosts you have to run, the more congested those CPUs become, and everything slows down. That may explain 'freeze' behavior. I've solved that problem by running deployment in parallel from multiple hosts (github actions) with |
Hi,
I'm experiencing a strange issue when using ansible 2.12.8 and later with mitogen 0.3.3.
When running my (quite long running) playbook on more than 8 hosts, mitogen exits on (quite random, like
hostname
,systemd
,service
,template
,make
, …) tasks (but all hosts at the same time) with:Running with 8 hosts or less or using ansible 2.12.7 and below works fine. Reducing ansible
forks
orMITOGEN_POOL_SIZE
doesn't help.I narrowed down the change in ansible that broke the playbook execution to ansible/ansible@45185b0 so reverting this commit fixes the problem.
Any ideas of what could be the incompatibility here?
The text was updated successfully, but these errors were encountered: