issue #139: mention relating buffering issue

wip-fakessh-exit-status
David Wilson 7 years ago
parent 1f1d691a28
commit 8f85943083

@ -123,9 +123,10 @@ High Risk
* Transfer of large (i.e. GB-sized) files using certain Ansible-internal APIs, * Transfer of large (i.e. GB-sized) files using certain Ansible-internal APIs,
such as triggered via the ``copy`` module, will cause corresponding temporary such as triggered via the ``copy`` module, will cause corresponding temporary
memory and CPU spikes on both host and target machine, due to delivering the memory and CPU spikes on both host and target machine, due to delivering the
file as a single large message. If many machines are targetted with a large file as a single large message, and quadratic buffer management in both
file, the host machine could easily exhaust available RAM. This will be fixed sender and receiver. If many machines are targetted with a large file, the
soon as it's likely to be tickled by common playbook use cases. host machine could easily exhaust available RAM. This will be fixed soon as
it's likely to be tickled by common playbook use cases.
* Situations may exist where the playbook's execution conditions are not * Situations may exist where the playbook's execution conditions are not
respected, however ``delegate_to``, ``connection: local``, ``become``, respected, however ``delegate_to``, ``connection: local``, ``become``,

Loading…
Cancel
Save