RabbitMQ cache grows really big

Troubleshooting
2

Hi @Wizzerinus

That is an strange behavior on the platform. The resource consumption of rabbitmq should be less.

Maybe they are creating a different vhost each time the service starts. Without reusing the existing one. For example

ls /var/lib/docker/volumes/taiga-docker_taiga-events-rabbitmq-data/_data/mnesia/

rabbit@07a159b2d29a
rabbit@07a159b2d29a-feature_flags
rabbit@07a159b2d29a-plugins-expand
rabbit@c9779ca3fd93
rabbit@c9779ca3fd93-feature_flags
rabbit@c9779ca3fd93.pid
rabbit@c9779ca3fd93-plugins-expand

## BAD: There are two vhosts here

If this happens, make sure you have the hostname defined in your services in docker-compose.yml.

  ...            
  taiga-async-rabbitmq:                                                                                                                                                                       
     image: rabbitmq:3.8-management-alpine                                                                                                                                                     
     hostname: "taiga-async-rabbitmq"  # <- HERE
     ...            
  ...            
  taiga-events-rabbitmq:                                                                                                                                                                       
     image: rabbitmq:3.8-management-alpine                                                                                                                                                     
     hostname: "taiga-events-rabbitmq"   # <- HERE
     ...

If this doesn’t fix the problem:

  • Can you paste the info of your docker repo
    cd taiga-docker
git describe --long
    …and the possible modifications you have made to the docker-compose.yml file?
  • Can you check and share the logs for those resources?

The events are useful for the interface to work in real time on the boards (kanban and taskboard). It is also used to manage asynchronous tasks (sending emails, background calculations, imports and exports, integrations, webhooks…).

You can delete these volumes so that they can be recreated, some notification or some async task (some email, some request to an external service -webhooks, integrations- ) may be lost. Although it is not recommended to do it very often, especially with the async service.

Best regards