it is basically a 'wait loop' but it does have some sleeps in there to avoid chewing on CPU, in your case the statement wil just do nothing for 20s and then wait for another 300 w/o doing anything. This path has no internal sleep in the loop (path and socket do) so that is probably why the CPU is being killed by a tight loop.
test out this PR and see if it fixes the issue for you https://github.com/ansible/ansible-modules-core/pull/1422 -- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJ5XC8mNicmR%2Bczi3FsLCRwjjrKpRnrj2cggyR-YujMnh0VHcA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
