Skip to content

Commit

Permalink
Update variables-deploy.md (magento#5333)
Browse files Browse the repository at this point in the history
* Update variables-deploy.md

* Update variables-deploy.md
  • Loading branch information
BaDos authored and hguthrie committed Sep 6, 2019
1 parent d920cd0 commit 632c7bf
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion guides/v2.2/cloud/env/variables-deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,10 @@ Configure how consumers process messages from the message queue by choosing one

- `false`—Consumers process available messages in the queue, close the TCP connection, and terminate. Consumers do not wait for additional messages to enter the queue, even if the number of processed messages is less than the `max_messages` value specified in the `CRON_CONSUMERS_RUNNER` deploy variable.

- `true`—Consumers continue to process messages from the message queue until reaching the maximum number of messages (`max_messages`) specified in the `CRON_CONSUMERS_RUNNER` deploy variable before closing the TCP connection and terminating the consumer process. If the queue empties before reaching `max_messages`, the consumer waits for more messages to arrive. If you use workers to run consumers instead of using a cron job, set this variable to true.
- `true`—Consumers continue to process messages from the message queue until reaching the maximum number of messages (`max_messages`) specified in the `CRON_CONSUMERS_RUNNER` deploy variable before closing the TCP connection and terminating the consumer process. If the queue empties before reaching `max_messages`, the consumer waits for more messages to arrive.

{: .bs-callout .bs-callout-warning}
If you use workers to run consumers instead of using a cron job, set this variable to true.

```yaml
stage:
Expand Down

0 comments on commit 632c7bf

Please sign in to comment.