Architecture
Monitoring
Benchmarking
Tools
Building a Release
Use
1
make rel
Copied!
to build a release.
It can be found under
_build/default/rel/antidote.Using a Release
After building a release with
make rel, Antidote can be started with the generated executable file. The release executable is located at _build/default/bin/rel/antidote/releases/bin/antidote. It should be started with the node name and cookie configured. Setting the cookie is optional, setting the node name is mandatory.1
# start antidote with given short node name as a foreground process
2
NODE_NAME=testing ./antidote foreground
3
4
# start antidote with given long node name with an erlang interactive console attached
5
NODE_NAME=testing ./antidote console
Copied!
Dynamic Release Configuration
The release executable is dynamically configurable with OS environment variables. The default configuration can be found in the config file folder
config. Only NODE_NAME, COOKIE, ROOT_DIR_PREFIX, LOGGER_DIR_PREFIX and DATA_DIR_PREFIX are expected to be provided via OS environment variables. All other configuration has to be set via erlang application environment arguments -Application Par Val, where variable expansion can be used in the Val part.Example:
1
# start antidote with a unified directory, set logging level to warning
2
# assume NODE_NAME, ROOT_PREFIX_DIR (`antidote/`), P1, P2, P3, P4, and P5 OS variables
3
# have been exported before
4
# modify appliation configurations (see sys.config.src and other .config files for options)
5
# logging level and all ports
6
# disable certification checks for concurrent transactions
7
./antidote foreground \
8
-kernel logging_level warning \
9
-riak_core handoff_port $P1 \
10
-ranch pb_port $P2 \
11
-antidote pubsub_port $P3 \
12
-antidote logreader_port $P4 \
13
-antidote_stats metrics_port $P5 \
14
-antidote txn_check false
Copied!
Last modified 2yr ago
Copy link