The broker

tip

The broker is the workflow orchestrator, in charge of database communication, sending punnets to the worker(s) for them to process the operations.

Configure the broker

Depending on the amount of documents you are dealing with, you may want to control max memory usage allowed (Xmx) for broker.

By default, only 1GB is allocated for this resource :

/config/env.properties

...
# Broker Maximum memory allowed (Xmx)
BROKER_MAX_MEMORY=1G

If the campaign are involving a couple of millions of documents, increasing this value to 8GB or 16GB will definitely help increasing the performance rate of the migration.

Configure the UI port

The UI port is also subject to configuration.

Fast2 application run on the 1789 port by default. To change this, add or update the parameters below:

/config/application.properties

...
# Remote broker port to use by the worker
# broker.port=1789
server.port=1789

Configure the content storage

When workers run with worker.content.factory=remote, they upload the contents they produce to the broker, and the broker writes them to disk. The root folder is set on the broker side:

/config/application.properties

...
# Root folder where the broker stores the contents uploaded by remote workers
broker.files.dir=files/

The default is files/, relative to the broker's working directory. Below that root the layout is fixed — <campaign>/<step name>/<documentId or punnetId> — and the worker-side worker.files.dir / worker.files.pattern properties do not apply. See File storage architecture on the worker page for the full local-vs-remote comparison.

Size the volume

All the content of every remote campaign accumulates under broker.files.dir. Keep it on a volume sized for the campaigns you run, or point it at one that is. DeleteContent does not clean this folder in remote mode: purge <broker.files.dir>/<campaign>/ once the campaign is finished.