Galaxy uses a message queue internally for communicating between processes. This is powered by the Kombu MQ library. For example, when reloading the toolbox or locking job execution, the process that handled that particular request will tell all others to also reload, lock jobs, etc.
This is configured via the amqp_internal_connection
galaxy.yml. For connection examples, see the Kombu connection documentation.
See the URL specification on that page for more information on configuring different transports.
By default, Galaxy will first attempt to use
your specified database_connection.
If that’s not specified either, Galaxy will automatically create and use a separate SQLite database located in your
Kombu and Galaxy support a variety of MQ transport/server options. RabbitMQ via AMQP is the most popular for production deployments.
Visit the Kombu reference index for a complete list of supported transports and their configuration.