You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ansible Project
Hi,
After upgrading to 2.0.0.2 I notice that there are 2 python processes "python /usr/bin/ansible-playbook stress.yml" taking up ~20% of the CPU each on the host machine that ran the playbook. Eating up resources like this for a long running playbook (I use playbooks to backup, and do virus scanning on a bunch of machines which can take hours) is not ideal. This didn't happen with 1.9.2.
Here's a basic playbook I used to reproduce this using gnu stress utility --- - hosts: stress tasks: - name: test shell: stress --cpu 8 --timeout 30s
Or command line: ansible stress -m shell -a "stress --cpu 8 --timeout 30s"
I notice this error on Ubuntu 15.10, Python 2.7.10. I'm using default ansible.cfg installed from PPA, with uncommeted "become=True" and "become_method=sudo".
Can anyone confirm the behavior? Any way I can fix this with configuration? Is this a bug?
Brian Coca
unread,
Jan 29, 2016, 5:20:05 PM1/29/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ansible Project
I would not call it a bug nor expected behavior but this is something
we should improve on, open a ticket on github using teh template and
minimal examples for us to reproduce.
--
Brian Coca
Budric
unread,
Jan 29, 2016, 5:51:12 PM1/29/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message