📄

High Availability and Scale with Traefik and MemSQL

Created

Jul 2, 2020 12:03 AM

Tags

Visionbox

By default the Visionbox uses a local binary file to store collections. If you want to have multiple Visionbox instances share one backend collection or if you want to enroll new images past a certain scale using a database backend might be a better option for you. This guide will explain how to do that. We'll be using docker compose to spin up a memsql and a visionbox container.

Let's get started.

Copy the following text into a file named visionbox-with-memsql-docker-compose.json.

version: '2.2'

networks:
  visionboxnet:
    driver: bridge

volumes:
  memsql_data_cpu:

services:
  reverse-proxy:
    image: traefik:v1.7
    # Enables the web UI and tells Traefik to listen to docker
    command: --api --docker
    labels:
      - "traefik.enable=true"
    ports:
      - 4000:80      
      - 4001:8080  # Traefik's web UI, enabled by --api
    volumes:
      # So that Traefik can listen to the Docker events
      - /var/run/docker.sock:/var/run/docker.sock
    depends_on:
      - visionbox
    networks:
      - visionboxnet

  visionbox:
    scale: 4
    labels:
      - "traefik.frontend.rule=Host:localhost"
    environment:
      - TOKEN=${TRUEFACE_TOKEN}
      - DB_USER=${DB_USER}
      - DB_PASSWORD=${DB_PASSWORD}
      - DB_HOST=${DB_HOST}
      - DB_PORT=${DB_PORT}
      - DB_NAME=${DB_NAME}
    image: "trueface/visionbox"
    restart: always
    expose:
        - "8080"
    networks:
      - visionboxnet
    depends_on:
      - memsql

  memsql:
    image: "memsql/cluster-in-a-box"
    restart: always
    user: root
    container_name: memsql
    networks:
      - visionboxnet
    volumes:
      - "memsql_data_cpu:/var/lib/memsql"
    ports:
      - "3306:3306"
      - "8081:8080"
    environment:
        - LICENSE_KEY=${MEMSQL_LICENSE_KEY}

Copy the following text into a file named .env and fill in your

Trueface Token
MemSQL License key which is free for Databases under 128GB
Database password of your choice

TRUEFACE_TOKEN=<your Trueface license token>
DB_HOST=memsql
DB_PORT=3306
DB_NAME=tfvision_dev
DB_USER=root
DB_PASSWORD=<your chosen DB password>
MEMSQL_LICENSE_KEY=<free for DBs up to 128GB of RAM usage, please contact support@trueface.ai if you need help with this, we're happy to help>

Start the containers

Keep in mind that the Visionbox container will try to connect to the DB with your password but the password hasn't been set on the Database yet. That's the next command after this one but until you've run that command you will see an error looping on your docker log output.

docker-compose -f visionbox-with-memsql-docker-compose.json up

Set the password on the MemSQL Database

export $(cat .env | xargs) && docker exec -it memsql /usr/bin/memsqlctl change-root-password --password $DB_PASSWORD -a --yes

Now that the password is set your visionbox container (which has been restarting in the background) will be able to connect to the Database.

Send your requests to the Load Balancer for distribution

The load balancer listens on port 4000 and distributes requests across the visionbox instances in the backend. So you can send your requests to http://localhost:4000/enroll for example.

You can now use the /enroll and /identify endpoints as you normally would or if you don't want to copy that code, using our Postman collection.

Please keep in mind the port now 4000 and not 8080 like in those examples so in the python example linked above you would replace the line which says

BASEURL = 'http://0.0.0.0:8080'

With

BASEURL = 'http://localhost:4000'

See what's going on in the database

To issue database commands directly, for example to change a label name or delete a feature you can now connect your mysql client (MemSQL is just MySQL with some additional vector math functions).

$ mysql -u root -p -h 127.0.0.1 -P 3306

# you will then be prompted for your DB password you set in the .env file earlier

# From here you can point the mysql client at your database
use <name of your database from the .env file, we used tfvision_dev by default>

MySQL [(none)]> use tfvision_dev;
Database changed

# I enrolled an image into a collection called home so you see the table here

MySQL [tfvision_dev]> show tables;
+------------------------+
| Tables_in_tfvision_dev |
+------------------------+
| collection             |
| detection              |
| frame                  |
| home                   |
| video                  |
| videopart              |
+------------------------+
6 rows in set (0.001 sec)

MySQL [tfvision_dev]> desc home;
+----------+-------------+------+------+---------+----------------+
| Field    | Type        | Null | Key  | Default | Extra          |
+----------+-------------+------+------+---------+----------------+
| Id       | bigint(20)  | NO   | PRI  | NULL    | auto_increment |
| label    | varchar(90) | YES  |      | NULL    |                |
| features | text        | YES  |      | NULL    |                |
| filepath | text        | YES  |      | NULL    |                |
+----------+-------------+------+------+---------+----------------+
4 rows in set (0.001 sec)

How is this getting load balanced?

The docker compose file uses a load balancer called traefik, it will distribute traffic across your visionbox instances following a round-robin schedule meaning the first request will go to node 1, the second to node 2. The fifth request will be sent to node 1 again.

You can check the status of your nodes on traefik's web interface by pointing a web browser at http://localhost:4001