Note that TDengine Server 3.0 uses TCP port 6030. Port 6041 is used by taosAdapter for the REST API service. Ports 6043 through 6049 are used by taosAdapter for other connectors. You can open these ports as needed.
If you need to persist data to a specific directory on your local machine, And then run the following command:
```shell
docker run -d-v ~/data/taos/dnode/data:/var/lib/taos \
* /var/lib/taos: TDengine's default data file directory. The location can be changed via [configuration file]. you can modify ~/data/taos/dnode/data to your own data directory
* /var/log/taos: TDengine's default log file directory. The location can be changed via [configure file]. you can modify ~/data/taos/dnode/log to your own log directory
:::
Run the following command to ensure that your container is running:
description:This chapter describes how to start and access TDengine in a Docker container.
---
...
...
@@ -10,8 +11,17 @@ This chapter describes how to start the TDengine service in a container and acce
The TDengine image starts with the HTTP service activated by default, using the following command:
```shell
docker run -d--name tdengine -p 6041:6041 tdengine/tdengine
docker run -d--name tdengine \
-v ~/data/taos/dnode/data:/var/lib/taos \
-v ~/data/taos/dnode/log:/var/log/taos \
-p 6041:6041 tdengine/tdengine
```
:::note
* /var/lib/taos: TDengine's default data file directory. The location can be changed via [configuration file]. you can modify ~/data/taos/dnode/data to your own data directory
* /var/log/taos: TDengine's default log file directory. The location can be changed via [configure file]. you can modify ~/data/taos/dnode/log to your own log directory
:::
The above command starts a container named "tdengine" and maps the HTTP service port 6041 to the host port 6041. You can verify that the HTTP service provided in this container is available using the following command.
...
...
@@ -283,32 +293,30 @@ services:
environment:
TAOS_FQDN:"td-1"
TAOS_FIRST_EP:"td-1"
ports:
-6041:6041
-6030:6030
volumes:
-taosdata-td1:/var/lib/taos/
-taoslog-td1:/var/log/taos/
# /var/lib/taos: TDengine's default data file directory. The location can be changed via [configuration file]. you can modify ~/data/taos/dnode1/data to your own data directory
-~/data/taos/dnode1/data:/var/lib/taos
# /var/log/taos: TDengine's default log file directory. The location can be changed via [configure file]. you can modify ~/data/taos/dnode1/log to your own log directory
-~/data/taos/dnode1/log:/var/log/taos
td-2:
image:tdengine/tdengine:$VERSION
environment:
TAOS_FQDN:"td-2"
TAOS_FIRST_EP:"td-1"
volumes:
-taosdata-td2:/var/lib/taos/
-taoslog-td2:/var/log/taos/
-~/data/taos/dnode2/data:/var/lib/taos
-~/data/taos/dnode2/log:/var/log/taos
td-3:
image:tdengine/tdengine:$VERSION
environment:
TAOS_FQDN:"td-3"
TAOS_FIRST_EP:"td-1"
volumes:
-taosdata-td3:/var/lib/taos/
-taoslog-td3:/var/log/taos/
volumes:
taosdata-td1:
taoslog-td1:
taosdata-td2:
taoslog-td2:
taosdata-td3:
taoslog-td3:
-~/data/taos/dnode3/data:/var/lib/taos
-~/data/taos/dnode3/log:/var/log/taos
```
:::note
...
...
@@ -382,24 +390,22 @@ networks:
services:
td-1:
image:tdengine/tdengine:$VERSION
networks:
-inter
environment:
TAOS_FQDN:"td-1"
TAOS_FIRST_EP:"td-1"
volumes:
-taosdata-td1:/var/lib/taos/
-taoslog-td1:/var/log/taos/
# /var/lib/taos: TDengine's default data file directory. The location can be changed via [configuration file]. you can modify ~/data/taos/dnode1/data to your own data directory
-~/data/taos/dnode1/data:/var/lib/taos
# /var/log/taos: TDengine's default log file directory. The location can be changed via [configure file]. you can modify ~/data/taos/dnode1/log to your own log directory
@@ -5,7 +5,7 @@ description: This document describes how to deploy a TDengine cluster on a serve
TDengine has a native distributed design and provides the ability to scale out. A few nodes can form a TDengine cluster. If you need higher processing power, you just need to add more nodes into the cluster. TDengine uses virtual node technology to virtualize a node into multiple virtual nodes to achieve load balancing. At the same time, TDengine can group virtual nodes on different nodes into virtual node groups, and use the replication mechanism to ensure the high availability of the system. The cluster feature of TDengine is completely open source.
This document describes how to manually deploy a cluster on a host as well as how to deploy on Kubernetes and by using Helm.
This document describes how to manually deploy a cluster on a host, deploy a cluster with Docker, and deploy a cluster with Kubernetes and Helm.
