Mike There are dedicated docs pages[1][2] for this topic. I must admit there is a fair bit of missing info in your query.
So to recap what we know: * ~16k hosts * forks set to 50 * unknown strategy * unknown config for async, throttle, serial and the other settings that can affect * unknown number of running ansible forks/processes on the control node * unknown if still polling for async * unknown other things as I am typing this in a hurry 1. https://docs.ansible.com/ansible/latest/user_guide/playbooks_async.html 2. https://docs.ansible.com/ansible/latest/user_guide/playbooks_strategies.html On Tue, Nov 1, 2022 at 10:48 AM Mike Eggleston <[email protected]> wrote: > I have my forks set to 50 in ~/.Ansible.CTG and the forks setting seems to > work for the first set of boxes, but doesn’t seem to work for the rest. I > thought the forks setting would keep $forks connections going until all > boxes in the inventory have been touched. > > Was I thinking wrong? (I’m running an ad hoc command on 16k boxes.) > > Mike > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/1EB21F73-144F-4F43-A696-0BA08D4CB2BA%40gmail.com > . > -- - Andrew "lathama" Latham - -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2Bqj4S-7xuwUmb02hjO2WbiVqr7PBbZgsoYm7tSMaheBxrO7wQ%40mail.gmail.com.
