Files
Flowise/docker/worker
nikitas-novatix eadf1b11b3 Fix: Add keep-alive options to Redis clients to prevent idle timeouts and socket closing. (#4377)
* redis keepalive mechanism for all redis

* removed offline queue commands

* Simplified changes for consistency. Added REDIS_KEEP_ALIVE env variable.

* update redis socket alive env variable

* lint fix

---------

Co-authored-by: Henry <hzj94@hotmail.com>
Co-authored-by: Henry Heng <henryheng@flowiseai.com>
2025-05-14 10:29:32 +08:00
..

Flowise Worker

By utilizing worker instances when operating in queue mode, Flowise can be scaled horizontally by adding more workers to handle increased workloads or scaled down by removing workers when demand decreases.

Heres an overview of the process:

  1. The primary Flowise instance sends an execution ID to a message broker, Redis, which maintains a queue of pending executions, allowing the next available worker to process them.
  2. A worker from the pool retrieves a message from Redis. The worker starts execute the actual job.
  3. Once the execution is completed, the worker alerts the main instance that the execution is finished.

How to use

Setting up Main Server:

  1. Follow setup guide
  2. In the .env.example, setup all the necessary env variables for QUEUE CONFIGURATION

Setting up Worker:

  1. Copy paste the same .env file used to setup main server. Change the PORT to other available port numbers. Ex: 5566
  2. docker compose up -d
  3. Open http://localhost:5566
  4. You can bring the worker container down by docker compose stop