diff options
| author | softwarefactory-project-zuul[bot] <softwarefactory-project-zuul[bot]@users.noreply.github.com> | 2019-05-28 22:15:26 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-05-28 22:15:26 +0200 |
| commit | 41f2b83ae2ec477c8d7719226a46095119eb48ce (patch) | |
| tree | 575509eaf79576bee40e7e4b26cd1937e07082a6 /docs | |
| parent | Merge pull request #3932 from shanemcd/zuul_k8s (diff) | |
| parent | add the ability to disable RabbitMQ queue durability (diff) | |
| download | awx-41f2b83ae2ec477c8d7719226a46095119eb48ce.tar.xz awx-41f2b83ae2ec477c8d7719226a46095119eb48ce.zip | |
Merge pull request #3947 from ryanpetrello/transient-queues
RFC: add the ability to disable RabbitMQ queue durability
Reviewed-by: https://github.com/softwarefactory-project-zuul[bot]
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/tasks.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/tasks.md b/docs/tasks.md index a84366b15b..74d824ac9f 100644 --- a/docs/tasks.md +++ b/docs/tasks.md @@ -28,6 +28,8 @@ To accomplish this, AWX makes use of a "Task Queue" abstraction. Task Queues ar AWX communicates with these worker processes to mediate between clients and workers. This is done via distributed RabbitMQ queues and the already-acknowledged local queue that the Dispatcher is working through. Simply put: to initiate a task, the client (generally, Python code in the AWX API) publishes a message to a queue, and RabbitMQ then delivers that message to one or more workers. +By default, when AWX creates queues in RabbitMQ, it creates them as *durable* queues in RabbitMQ (which allows for message persistence at the cost of lower performance). For increased message throughput (at the risk of message loss on server restarts), set BROKER_DURABILITY=False, and AWX will create _transient_ queues instead. + Clustered AWX installations consist of multiple workers spread across every node, giving way to high availability and horizontal scaling. |