--- title: "Deploy in distributed mode in Docker" description: "Guide to deploying a distributed Trino cluster and Aerospike connector using Docker images." --- # Deploy in distributed mode in Docker > For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt) > > All documentation pages available in markdown. In distributed mode, you use the Docker image that you built in [Deploy Trino clusters and Trino connector in Docker](https://aerospike.com/docs/connectors/trino/docker) to create: - A container that runs the Trino connector and the coordinator node of a Trino cluster. - One or more containers that each run the Trino connector and a worker node of the Trino cluster. Distributed mode is more suitable for production environments than standalone mode. ## Prerequisite - Build an image of Trino and the Trino connector, as described in [Deploy Trino clusters and Trino connector in Docker](https://aerospike.com/docs/connectors/trino/docker). - Ensure that you have access to Docker Hub or a custom Docker registry, and place the image either in Docker Hub or in the registry, so that each Trino worker node that you start has access to it. ## Options for running a distributed environment There are two options: - [Prerequisite](#prerequisite) - [Options for running a distributed environment](#options-for-running-a-distributed-environment) - [Procedure for using environment variables to configure the Trino connector](#procedure-for-using-environment-variables-to-configure-the-trino-connector) - [Start a coordinator node](#start-a-coordinator-node) - [Start a worker node](#start-a-worker-node) - [Procedure for configuring the Trino connector through a configuration file](#procedure-for-configuring-the-trino-connector-through-a-configuration-file) - [Set values in the aerospike.properties file](#set-values-in-the-aerospikeproperties-file) - [Create a container and start the coordinator](#create-a-container-and-start-the-coordinator) - [Start one or more worker nodes](#start-one-or-more-worker-nodes) ## Procedure for using environment variables to configure the Trino connector Consider using this option when you do not plan to use an `aerospike.properties` file. Running a Trino cluster and the Trino connector this way can help you rapidly prototype running SQL queries against your Aerospike cluster. ### Start a coordinator node Run a `docker run` command to start a container that hosts and starts the coordinator node. The [environment variables](https://aerospike.com/docs/connectors/trino/docker/env) let you specify values for a subset of the connector settings that the [configuration properties](https://aerospike.com/docs/connectors/trino/config) cover. Use the `-e` option for each environment variable that you want to include. - Include the `AS_HOSTLIST` environment variable. - Include the `TRINO_NODE_TYPE` environment variable and set it to `coordinator`. Here is an example, where - `--rm` specifies to remove the container automatically when the command exits. - `-p 8080:8080` binds port 8080 of the container to port 8080 of the host system. - `` is the name given to reference the container within a Docker network. - `` is the name given to the Docker image when it was built. ```plaintext docker run --rm -p 8080:8080 -e AS_HOSTLIST=docker.for.mac.host.internal:3000 -e TRINO_NODE_TYPE=coordinator --name ``` If you configured Trino properties, include this option to mount the files into the `/etc/trino` directory in the container: ```plaintext -v /docker/etc:/etc/trino ``` where `/docker/etc` is the path of the directory in which the configuration files that you edited are located in `trino-aerospike.docker`, the repository that you cloned in a previous step. If the Trino configuration files that you edited are in a different directory, use the path of that directory, instead. You can even mount individual files, as in this example: ```plaintext -v /docker/etc/log.properties:/etc/trino/log.properties ``` If you are providing the Trino schemas, include this option to mount the files into the `/etc/trino/aerospike` directory in the container: ```plaintext -v :/etc/trino/aerospike ``` where `` is the path of the folder on your system in which you placed the JSON files. ### Start a worker node Run a `docker run` command to start a container that hosts and starts a worker node, or run a bash script if you want to start multiple worker nodes, each in a separate container. Use the same command that you used to start the coordinator node. However, change the value of the environment variable `TRINO_NODE_TYPE` to `worker`. You must also set a value for the `TRINO_DISCOVERY_URI` environment variable if you set a non-default URI for the coordinator node. You can set this URI in the Trino configuration file `config.properties` in step 3 of [Deploy Trino clusters and Trino connector in Docker](https://aerospike.com/docs/connectors/trino/docker). The default is `http://localhost:8080`. When you specify the URI in a web browser, Trino shows you a dashboard with which you can monitor the health of your distributed cluster. If you want to create a bash script to start multiple worker nodes, ensure that each instance of the `docker run` command has a different value for the `--name` option. For example, your bash script might look like this, where `trino-aerospike` is the name of the Docker image: ```plaintext docker run --rm -p 8080:8080 -e AS_HOSTLIST=docker.for.mac.host.internal:3000 -e TRINO_NODE_TYPE=worker --name trino-worker-1 trino-aerospike docker run --rm -p 8080:8080 -e AS_HOSTLIST=docker.for.mac.host.internal:3000 -e TRINO_NODE_TYPE=worker --name trino-worker-2 trino-aerospike docker run --rm -p 8080:8080 -e AS_HOSTLIST=docker.for.mac.host.internal:3000 -e TRINO_NODE_TYPE=worker --name trino-worker-3 trino-aerospike docker run --rm -p 8080:8080 -e AS_HOSTLIST=docker.for.mac.host.internal:3000 -e TRINO_NODE_TYPE=worker --name trino-worker-4 trino-aerospike ``` ## Procedure for configuring the Trino connector through a configuration file With this option, you configure the connector by setting values for its configuration properties in the `aerospike.properties` file. The number of properties that you can configure with this file is greater than the number that you can configure with the environment variables. When you run the `docker run` command, you mount that file’s directory in the container that the command creates. ### Set values in the aerospike.properties file Set values for [configuration properties](https://aerospike.com/docs/connectors/trino/config) in `aerospike.properties`. In the repository that you cloned in a previous step, the path to this file is `/trino-aerospike.docker/docker/etc/catalog/aerospike.properties`. By default, the file in the repository includes these two entries. If you are running Docker on Linux, replace `docker.for.mac.host.internal` with `localhost`. ```plaintext connector.name=aerospike aerospike.hostlist=docker.for.mac.host.internal:3000 ``` If you have an existing `aerospike.properties` file that you want to use, be sure to change the value of `aerospike.hostlist`. ### Create a container and start the coordinator Run the `docker run` command to create a container and to start the coordinator node and the Trino connector within the container. To mount the `aerospike.properties` file into the `/etc/trino/catalog` directory in the container, use the following command: ```plaintext docker run --rm -p 8080:8080 -e TRINO_NODE_TYPE=coordinator -v :/etc/trino/catalog/aerospike.properties \ --name ``` where: - `--rm` specifies to remove the container automatically when the command exits. - `-p 8080:8080` binds port 8080 of the container to port 8080 of the host system. - `` is the path to the `aerospike.properties` file on your system. - `` is the name given to reference the container within a Docker network. - `` is the name given to the Docker image when it was built. If you configured Trino properties, include this option to mount the files into the `/etc/trino` directory in the container: ```plaintext -v /docker/etc:/etc/trino ``` where `/docker/etc` is the path of the directory in which the configuration files that you edited are located in `trino-aerospike.docker`, the repository that you cloned in a previous step. If the Trino configuration files that you edited are in a different directory, use the path of that directory, instead. You can even mount individual files, as in this example: ```plaintext -v /docker/etc/log.properties:/etc/trino/log.properties ``` If you are providing the Trino schemas, include this option to mount the files into the `/etc/trino/aerospike` directory in the container: ```plaintext -v :/etc/trino/aerospike ``` where `` is the path of the folder on your system in which you placed the JSON files. ### Start one or more worker nodes Run the same `docker run` command that you used to start the coordinator node. However, change the value of the environment variable `TRINO_NODE_TYPE` to `worker`. You must also set a value for the `TRINO_DISCOVERY_URI` environment variable if you set a non-default URI for the coordinator node. You can set this URI in the Trino configuration file `config.properties` in step 3 of [Deploy Trino clusters and Trino connector in Docker](https://aerospike.com/docs/connectors/trino/docker). The default is `http://localhost:8080`. When you specify the URI in a web browser, Trino shows you a dashboard with which you can monitor the health of your distributed cluster. If you want to create a bash script to start multiple worker nodes, ensure that each instance of the `docker run` command has a different value for the `--name` option. For example, your bash script might look like this, where `trino-aerospike` is the name of the Docker image: ```plaintext docker run --rm -p 8080:8080 -e TRINO_NODE_TYPE=worker -v $HOME/Documents/Trino/docker/etc/catalog:/etc/trino/catalog \ -v "$(pwd)"/docker/etc/aerospike:/etc/trino/aerospike --name trino-worker-1 trino-aerospike docker run --rm -p 8080:8080 -e TRINO_NODE_TYPE=worker -v $HOME/Documents/Trino/docker/etc/catalog:/etc/trino/catalog \ -v "$(pwd)"/docker/etc/aerospike:/etc/trino/aerospike --name trino-worker-2 trino-aerospike docker run --rm -p 8080:8080 -e TRINO_NODE_TYPE=worker -v $HOME/Documents/Trino/docker/etc/catalog:/etc/trino/catalog \ -v "$(pwd)"/docker/etc/aerospike:/etc/trino/aerospike --name trino-worker-3 trino-aerospike docker run --rm -p 8080:8080 -e TRINO_NODE_TYPE=worker -v $HOME/Documents/Trino/docker/etc/catalog:/etc/trino/catalog \ -v "$(pwd)"/docker/etc/aerospike:/etc/trino/aerospike --name trino-worker-4 trino-aerospike ```