ArangoDB Server Foxx Options

enable or disable the Foxx service propagation on startup

if true, all Foxx services in all databases will be synchronized between multiple coordinators during the boot sequence. This ensures that all Foxx services are up-to-date when a coordinator reports itself as ready.

In case the option is set to (i.e. no waiting), the coordinator will complete the boot sequence faster, and the Foxx services will be propagated lazily. Until the initialization procedure has completed for the local Foxx apps, any request to a Foxx app will be responded to with an HTTP 500 error and message

When not using Foxx, this option should be set to false to benefit from a faster coordinator startup. Deployments relying on Foxx apps being available as soon as a coordinator is integrated or responding should set this option to true (which is the default value).

The option only has an effect for cluster setups. On single servers and in active failover mode, all Foxx apps will be available from the very beginning.

Note: ArangoDB 3.8 changes the default value to false for this option.

If true, the Foxx queues will be available and jobs in the queues will be executed asynchronously.

The default is true. When set to the queue manager will be disabled and any jobs are prevented from being processed, which may reduce CPU load a bit.

poll interval for Foxx queues

The default is 1 second. If Foxx queues are not used much, then this value may be increased to make the queues thread wake up less.