engineering/unrhodecode
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

packages: updated celery to 4.3.0 and switch default backend to redis

Browse source 
- we usually have redis, and it makes our stack simpler and easier to debug.
This commit is contained in:
Marcin Kuzminski 2019-09-03 11:42:10 +02:00
parent 483b3813b0
commit 633c58187e
7 changed files with 94 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/admin/system_admin/tuning/tuning-scale-horizontally-cluster.rst
View file

@ -57,7 +57,7 @@ Here's an overview what components should be installed/setup on each server in o
- `nginx` acting as a load-balancer.
- `postgresql-server` used for database and sessions.
- `redis-server` used for storing shared caches.
- optionally `rabbitmq-server` for `Celery` if used.
- optionally `rabbitmq-server` or `redis` for `Celery` if used.
- optionally if `Celery` is used Enterprise/Community instance + VCSServer.
- optionally mailserver that can be shared by other instances.
- optionally channelstream server to handle live communication for all instances.
@ -372,16 +372,16 @@ Using Celery with cluster
If `Celery` is used we recommend setting also an instance of Enterprise/Community+VCSserver
on the node that is running `RabbitMQ`_. Those instances will be used to executed async
tasks on the `rc-node-1`. This is the most efficient setup. `Celery` usually
handles tasks such as sending emails, forking repositories, importing
on the node that is running `RabbitMQ`_ or `Redis`_. Those instances will be used to
executed async tasks on the `rc-node-1`. This is the most efficient setup.
`Celery` usually handles tasks such as sending emails, forking repositories, importing
repositories from external location etc. Using workers on instance that has
the direct access to disks used by NFS as well as email server gives noticeable
performance boost. Running local workers to the NFS storage results in faster
execution of forking large repositories or sending lots of emails.
Those instances need to be configured in the same way as for other nodes.
The instance in rc-node-1 can be added to the cluser, but we don't recommend doing it.
The instance in rc-node-1 can be added to the cluster, but we don't recommend doing it.
For best results let it be isolated to only executing `Celery` tasks in the cluster setup.