AllQ
  • What is AllQueue?
  • Getting Started
  • Install
    • Why AllQueue?
    • Architecture
    • 1. Install AllQueue Server
    • 2. Install AllQueue Client
    • Installation (Quick Start)
  • Foundational Concepts
    • Talking to AllQueue
    • Server/Client
    • Jobs
    • Tubes
    • Persistence
  • Features
    • Autobury Failed Jobs
    • Delayed Jobs/Scheduling
    • Priority
    • Workflow
    • Throttle
    • Fair Queuing
  • Configuration
  • Rest API Usage
  • Scenarios
  • Advanced
    • Docker Configuration Options
    • Federation Deployment
Powered by GitBook
On this page
  • AllQueue Server
  • AllQueue Client

Was this helpful?

  1. Advanced

Docker Configuration Options

ENV vars and Docker setting for your deployments

There are numerous ENV variable you can use to configure your AllQServer and Clients

AllQueue Server

ENV variables you can set on your Docker container:

  • SERVER_PORT (Port to listen on, default = 5555)

  • SERIALIZE (true or false to persist jobs locally for restartability, default = false)

  • SERIALIZER_DIR (location of serialized files, default = /tmp/allq)

  • DEBUG (true or false to log more verbosely, default = false)

  • CONFIG_ONLY (true or false to only generate new keys, default = false)

  • DEFAULT_TTL (default time to live in seconds, default = 3600)

  • PRIORITY_SIZE (range of priorities 1 -> PRIORITY_SIZE, default = 10)

  • FQ_SHARD_COUNT (number of sub-queues to allow for sharding, default = 10)

  • FQ_PREFIX (prefix required to identify fair queue tubes, default = 'fq-')

AllQueue Client

ENV variables you can set on your Docker container:

  • HTTP_SERVER_PORT (Http REST API port, default = 8090)

  • TCP_CLIENT_PORT (For TCP Clients, default = 7766)

  • SERVER_STRING (Comma separated list of AllQ Servers)

  • ALLQ_DEBUG (true or false to log more verbosely, default = false)

An example server docker run command might look like this

docker run --name=allq_server -d \
  -p 5555:5555 \
  --restart=unless-stopped \
  -e "A_CURVE_SECRETKEY=$A_CURVE_SECRETKEY" \
  -e "A_CURVE_PUBLICKEY=$A_CURVE_PUBLICKEY" \
  -e "SERIALIZE=true" \
  -e "DEBUG=true" \
  -v /tmp:/tmp \
  --init \
  --sysctl net.core.somaxconn=1028 \
  blitline/allq:server_latest

The above example would let you run a persistent storage docker server where your peristence files would live on your host machine at /tmp/allq.

PreviousScenariosNextFederation Deployment

Last updated 3 years ago

Was this helpful?