Skip to content

dtable-server cluster (optional)

The dtable-server is stateful. A base should only be loaded into one server and write to that server. Every base has an UUID. The bases are distributed to different dtable-server according to the first 2 character in its UUID. So there are 256 buckets. The dtable-server servers should know the distribution map consistently. We use Etcd server to achieve the goal.

When a dtable-server join to the cluster, it register its information to Etcd cluster. When a dtable-server is dead, the registered information will expire in 90 seconds. A separate cluster monitor program will periodically check available servers and assign buckets to different dtable-servers (it will keep existing assignment as much as possible to keep the assignment stable), and write the new assignment information to Etcd. When the assignment is changed, the dtable-servers will receive real-time notification from Etcd.

When a base is visted by a user, the dtable-web will check the information in Etcd and return the corresponding dtable-server to the browser. The browser then loads the base from the dtable-server and establishes a Socket connection for real-time communication.

For internal communication, dtable-web, dtable-event, dtable-db use dtable-server-proxy node, instead of talking to a specific dtable-server directly.

Here we use two dtable-server nodes, one dtable-server-proxy node and three Etcd servers as an example to show how to setup the cluster.


  • dtable-server-01
  • dtable-server-02
  • dtable-server-proxy
  • etcd-01
  • etcd-02
  • etcd-03

Note: You need to deploy at least two dtable-server nodes according to the Setup dtable-server chapter in the previous manual.



# install
sudo apt install -y etcd etcd-client

# start
service etcd start

ETCD cluster

Guide to setting up a cluster in etcd

Deploy dtable-server-proxy by docker

Download the docker-compose.yml sample file into dtable-server-proxy's directory and modify the Compose file to fit your environment and settings.

mkdir -p /opt/dtable-server-proxy/

Optional customizable options in the Compose file are:

  • Volume path for the container dtable-server-proxy
  • Image tag of the dtable-server-proxy version to install (image)
  • Time zone (TIME_ZONE)

Note: dtable-server-proxy only needs LAN communication, public domain is not required.

Create dtable-server-proxy configuration file

Prepare configuration file directory

mkdir -p /opt/dtable-server-proxy/shared/seatable-proxy/conf/

Create the dtable-server-proxy configuration file : /opt/dtable-server-proxy/shared/seatable-proxy/conf/dtable_server_config.json

  "cluster_config": {
    "etcd_host_list": ["", "", ""]  // domain of etcd servers

Start dtable-server-proxy

docker compose up -d

Modify dtable-server-01 configuration file


  "cluster_config": {
    "etcd_host_list": ["", "", ""],  // domain of etcd servers
    "node_id": "dtable-server-01",
    "node_url": "",  // domain of dtable-server-01
    "local_node_url": ""  // intranet IP of dtable-server-01

Then restart dtable-server-01

docker exec -d seatable /shared/seatable/scripts/ restart

Note, the node_url is used by the end user to connect to the server. The local_node_url is used by the dtable-server-proxy to connect to the server.

Modify dtable-server-02 configuration file


  "cluster_config": {
    "etcd_host_list": ["", "", ""],  // domain of etcd servers
    "node_id": "dtable-server-02",
    "node_url": "",  // domain of dtable-server-02
    "local_node_url": ""  // intranet IP of dtable-server-02

Then restart dtable-server-02, the command is the same as before.

Modify dtable-web configuration files

# etcd
ETCD_SERVER_HOST_LIST = ['', '', '']  # domain of etcd servers
DTABLE_PROXY_SERVER_URL = ''  # domain of dtable-server-proxy


[dtable cache]
dtable_server_url = ""  # domain of dtable-server-proxy

Then restart dtable-web, the command is the same as before.

Now you can use the dtable-server cluster.

Load balance

In some cases, you can manually load balancing

curl -X POST  # domain of dtable-server-proxy