From b55cc61ef00443f66872ed124805b8bf42ed1a11 Mon Sep 17 00:00:00 2001 From: Sam Doran Date: Fri, 8 Dec 2017 12:09:38 -0500 Subject: [PATCH] Clarify docs to explain that max_fail_percentage uses batch size (#33720) --- docs/docsite/rst/playbooks_delegation.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docsite/rst/playbooks_delegation.rst b/docs/docsite/rst/playbooks_delegation.rst index fe8394836b5..f23a4116881 100644 --- a/docs/docsite/rst/playbooks_delegation.rst +++ b/docs/docsite/rst/playbooks_delegation.rst @@ -80,9 +80,9 @@ You can also mix and match the values:: Maximum Failure Percentage `````````````````````````` -By default, Ansible will continue executing actions as long as there are hosts in the group that have not yet failed. -In some situations, such as with the rolling updates described above, it may be desirable to abort the play when a -certain threshold of failures have been reached. To achieve this, as of version 1.3 you can set a maximum failure +By default, Ansible will continue executing actions as long as there are hosts in the batch that have not yet failed. The batch size for a play is all the hosts specified in the ``hosts:`` field. +In some situations, such as with the rolling updates described above, it may be desirable to abort the play when a +certain threshold of failures have been reached. To achieve this, you can set a maximum failure percentage on a play as follows:: - hosts: webservers