Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mitogen
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Commits
Open sidebar
nexedi
mitogen
Commits
67ff762b
Commit
67ff762b
authored
Mar 16, 2018
by
David Wilson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
issue #139: docs: remove note about bad buffering
parent
eba12e2e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
4 deletions
+3
-4
docs/ansible.rst
docs/ansible.rst
+3
-4
No files found.
docs/ansible.rst
View file @
67ff762b
...
@@ -126,10 +126,9 @@ High Risk
...
@@ -126,10 +126,9 @@ 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, and quadratic buffer management in both
file as a single large message. If many machines are targetted with a large
sender and receiver. If many machines are targetted with a large file, the
file, the host machine could easily exhaust available RAM. This will be fixed
host machine could easily exhaust available RAM. This will be fixed soon as
soon as it's likely to be tickled by common playbook use cases.
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``,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment