Last weekend I re-stumbled across ActorDB, a very interesting distributed database system that scales near linearly by scoping work to Actors. Every database action, whether that's an insert, select, update, delete or whatnot, always starts by specifying the Actor. This effectively scopes the changes to a single database, which then replicates to its sibling databases on other ActorDB nodes in a cluster. There's a lot more to it than that, as you can of course work with multiple actors within a transaction, and can connect to any node, in any cluster, and the data will be routed properly. In short, think user-centric databases all clustered and replicated together, using the SQLite engine backed by LMDB storage and using Raft for consensus. There's a little buzz-word bingo for you.
ActorDB
SQLite
LMDB
Raft
After reading everything I could find on ActorDB, and still having a bit of time to kill before having to go transfer our daughter from one place to another yet again, I figured I'd have a quick play with it.
As is rapidly becoming my norm, I went to Docker Hub to find a Docker image to spin up. To my utter shock and horror (there might be a little bit of exaggeration there), there was not a single image for ActorDB to be found!
Docker Hub
Docker
My first thought was that maybe there was a very good reason for there not being a Docker image available, but after a little look around that there interwebs I came to the conclusion that it was simply because it's a young project, and generally run on real machines in production. Nothing made me think it was a terrible idea to run ActorDB in a Docker container, so why not give it a bash? ActorDB for Docker was born!
ActorDB for Docker
The Dockerfile
Having recently done a bunch of work for Delicious Brains that involved using Docker, I wasn't too phased by the idea of spinning up a new Dockerfile, and luckily there's an ActorDB package for Debian.
Delicious Brains
Dockerfile
ActorDB package for Debian
I built a basic image based on Debian Jessie, and then logged into it and experimented with the steps I needed to run to get ActorDB installed and running. It took much less time than I expected as ActorDB is pretty self contained, the biggest issues I had were with making sure curl had all its dependencies in place to actually download the .deb file from within the running container (it needs some extra root certificates installed via a package).
Debian Jessie
I also rather stupidly forgot that the actordb program runs as a daemon by default, so the container kept just running and exiting cleanly. Once I realised what was going on, I simply ran the container with –entrypoint /bin/bash and then ran actordb without any arguments to get its usage info. Turns out you can run actordb forground rather than actordb start to get it to run in the current shell. Just what I needed.
I've been working with a PhantomJS image recently, and noticed that it used a script to ensure that the phantomjs binary did not run as the first process in the container (PID 1) as it may cause issues with shutting it down. So I nicked that idea.
PhantomJS image
The final Dockerfile is pretty simple, makes sure to expose the required ports and volume primary paths that ActorDB uses, and the image is available as an automated build on Docker Hub.
Final Dockerfile
Automated build on Docker Hub
Docker Compose
A distributed database is no good without multiple nodes to distribute its data around, and of course I wanted to ensure the image could be used in a network of containers. I used Docker Compose to set up a very rudimentary cluster of three nodes, you can see the setup in the project root's docker-compose.yml file.
Docker Compose
docker-compose.yml
While the containers seemed to work (on second start, see issue #1 for details), could ping each other by their service names (e.g. actordb-server-1 could ping actordb-server-2), I spent ages trying to get the instances of ActorDB to actually replicate data between them. I eventually sorted it out with the following two important realisations:
Issue #1
1. The -name setting in each node's vm.args file must have a unique name before the @, the ip address/domain name after the @ doesn't make it unique.
vm.args
2. You must update your initialisation script that is run on the leader to also register the other nodes in the cluster (you can register them manually later, but will need to copy the leader's lmdb file to them first).
initialisation script
Once I'd worked that out, I was super happy to have a fully working cluster of ActorDB nodes!
Quick Example
The following text is a quick run through of bringing up a cluster, initialising it, writing some data to the first node, switching to the second node and showing the data replicated from the first, creating some more data, and then showing it all on the third node, but using the MySQL client. Enjoy!
Ians-MBP:actordb-for-docker ian$ ./up.sh
Creating network actordbfordocker_default with the default driver
Creating actordbfordocker_actordb-server-1_1
Creating actordbfordocker_actordb-server-2_1
Creating actordbfordocker_actordb-server-3_1
actordb-server-1 – Use actordb_console to run the SQL script that initialises the database:
Ians-MBP:actordb-for-docker ian$ docker-compose exec actordb-server-1 actordb_console -f /etc/actordb/init.example.sql
Config updated.
Config updated.
Schema updated.
actordb-server-1 – Use actordb_console to show the schema, create and select some data:
Ians-MBP:actordb-for-docker ian$ docker-compose exec actordb-server-1 actordb_console -u myuser -pw mypass
*******************************************************************
Databases:
use config (use c) initialize/add nodes and user account management
use schema (use s) set schema
use actordb (use a) (default) run queries on database
*******************************************************************
Commands:
open (windows only) open and execute .sql file
q exit
h print this header
commit (c) execute transaction
rollback (r) abort transaction
print (p) print transaction
show (s) show schema
show status show database status
show queries show currently running queries
show shards show shards on node
*******************************************************************
actordb> actor type1(hello_world);
actordb (1)> insert into tab(id, txt) values(1,"Hello World");
actordb (2)> c
Error: {error,{nocreate,>}}
actordb> show
****************************************************************************************************************************************************************
sql type |
----------------------------------------------------------------------------------------------------------------------------------------------------------------
$CREATE TABLE tab (id INTEGER PRIMARY KEY, txt TEXT); type1 |
$CREATE TABLE tab1 (id INTEGER PRIMARY KEY, txt TEXT); type1 |
$ALTER TABLE tab ADD i INTEGER; type1 |
$CREATE TABLE tabx (id INTEGER PRIMARY KEY CHECK (typeof(id) == "integer"), txt TEXT CHECK (typeof(id) == "text")); type1 |
$CREATE TABLE asdf (id INTEGER PRIMARY KEY AUTOINCREMENT, txt BLOB); type2 |
$CREATE TABLE actors (id TEXT PRIMARY KEY, hash INTEGER, val INTEGER) WITHOUT ROWID; counters |
$CREATE TABLE actors (id TEXT PRIMARY KEY, hash INTEGER, size INTEGER) WITHOUT ROWID; filesystem |
$CREATE TABLE users (id INTEGER PRIMARY KEY AUTOINCREMENT, fileid TEXT, uid INTEGER, FOREIGN KEY (fileid) REFERENCES actors(id) ON DELETE CASCADE); filesystem |
----------------------------------------------------------------------------------------------------------------------------------------------------------------
actordb> actor type1(hello_world) create;
actordb (1)> insert into tab(id, txt) values(1,"Hello World");
actordb (2)> c
Rowid: 1, Rows changed: 1
actordb> actor type1(hello_world) create;
actordb (1)> select * from tab;
actordb (2)> c
*********************
i id txt |
---------------------
null 1 Hello World |
---------------------
actordb> q
Bye!
actordb-server-2 – Use actordb_console to see the data created on actordb-server-1, and create some more:
Ians-MBP:actordb-for-docker ian$ docker-compose exec actordb-server-2 actordb_console -u myuser -pw mypass
*******************************************************************
Databases:
use config (use c) initialize/add nodes and user account management
use schema (use s) set schema
use actordb (use a) (default) run queries on database
*******************************************************************
Commands:
open (windows only) open and execute .sql file
q exit
h print this header
commit (c) execute transaction
rollback (r) abort transaction
print (p) print transaction
show (s) show schema
show status show database status
show queries show currently running queries
show shards show shards on node
*******************************************************************
actordb> actor type1(hello_world) create;
actordb (1)> select * from tab;
actordb (2)> c
*********************
i id txt |
---------------------
null 1 Hello World |
---------------------
actordb> actor type1(hello_world) create;
actordb (1)> insert into tab(id, txt) values(2, "ActorDB Rules!");
actordb (2)> c
Rowid: 2, Rows changed: 1
actordb> q
Bye!
actordb-server-3 – Use the mysql client to connect to actordb-server-3's MySQL protocol port:
Ians-MBP:actordb-for-docker ian$ mysql -u myuser -p -h127.0.0.1 -P33337
Enter password:
Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 0
Server version: 5.5.0-myactor-proto 5.5.0-myactor-proto
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type "help;" or "h" for help. Type "c" to clear the current input statement.
mysql> actor type1(hello_world) create; select * from tab;
Query OK, 0 rows affected (0.01 sec)
+------+----------------+------+
| id | txt | i |
+------+----------------+------+
| 1 | Hello World | NULL |
| 2 | ActorDB Rules! | NULL |
+------+----------------+------+
2 rows in set (0.00 sec)
mysql> actor type1(hello_world) create; update tab set i = id * 100;
Query OK, 0 rows affected (0.00 sec)
Query OK, 2 rows affected (0.02 sec)
mysql> actor type1(hello_world) create; select * from tab;
Query OK, 0 rows affected (0.01 sec)
+------+----------------+------+
| id | txt | i |
+------+----------------+------+
| 1 | Hello World | 100 |
| 2 | ActorDB Rules! | 200 |
+------+----------------+------+
2 rows in set (0.00 sec)
mysql> exit;
Bye
