Hi @haishui126,

1. do you use the docker compose manifest for one or multiple tablet servers? if it is the one for one tablet server, there seems to be an error in the docker compose manifest. the command of the tablet-server should be command: tabletServer and not command: tabletServer:0.5.0.

Fixed docker-compose.yml for a single tablet server:

services:
  coordinator-server:
    image: fluss/fluss:0.5.0
    command: coordinatorServer
    depends_on:
      - zookeeper
    environment:
      - |
        FLUSS_PROPERTIES=
        zookeeper.address: zookeeper:2181
        coordinator.host: coordinator-server
        remote.data.dir: /tmp/fluss/remote-data
  tablet-server:
    image: fluss/fluss
    command: tabletServer  # << LINE TO BE FIXED
    depends_on:
      - coordinator-server
    environment:
      - |
        FLUSS_PROPERTIES=
        zookeeper.address: zookeeper:2181
        tablet-server.host: tablet-server
        tablet-server.id: 0
        kv.snapshot.interval: 0s
        data.dir: /tmp/fluss/data
        remote.data.dir: /tmp/fluss/remote-data
    volumes:
      - shared-tmpfs:/tmp/fluss
  zookeeper:
    restart: always
    image: zookeeper:3.9.2

volumes:
  shared-tmpfs:
    driver: local
    driver_opts:
      type: "tmpfs"
      device: "tmpfs"

Run docker compose up -d and check with docker ps -a if all servers are running.

2. Regarding this

add ports: - "9123:9123" for coordinator-server and deploy to server

and this

sql-client error log: Caused by: com.alibaba.fluss.exception.NetworkException: Disconnected from node 192.168.0.3:9123 (id: cs--1)

can you explain in more detail what you are trying to achieve? does this guide solve your problem?

Hi @michaelkoepf.
I fixed the command before I started the service. My compose file is the same with you.
I added ports: - "9123:9123" to enable access to the Fluss service from outside my server.

My server's external IP address is 10.xx.xx.xx, but the host address registered to zk is 192.168.xx.xx, which is the container ip.
The ip registered to zk is from com.alibaba.fluss.rpc.netty.server.NettyServer#getHostname.

This guide works well, beceuse flink and fluss is in the same docker service. They can communicate with each other using their container IP.

ok. this means you run fluss with the docker compose manifest and flink and the sql client somewhere outside (on the same or even a different host), right?

how do you create the fluss catalog in the sql client? have you adapted the bootstrap.server option accordingly (see below)?

CREATE CATALOG my_fluss WITH (
    'type' = 'fluss',
    'bootstrap.servers' = '10.XXX.XXX.XXX:9123'
);

ok. this means you run fluss with the docker compose manifest and flink and the sql client somewhere outside (on the same or even a different host), right?

how do you create the fluss catalog in the sql client? have you adapted the bootstrap.server option accordingly (see below)?

CREATE CATALOG my_fluss WITH (
    'type' = 'fluss',
    'bootstrap.servers' = '10.XXX.XXX.XXX:9123'
);

right. the following is my code, the connection timed out when creating the database

        StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment();
        StreamTableEnvironment tableEnv = StreamTableEnvironment.create(env);
        tableEnv.executeSql("CREATE CATALOG fluss_catalog WITH (\n" +
                "   'type' = 'fluss',\n" +
                "   'bootstrap.servers' = '10.xxx.xxx.xxx:9123'\n" +
                ");\n");

        tableEnv.executeSql("USE CATALOG `fluss_catalog`;");
        tableEnv.executeSql("CREATE DATABASE `db_test`;");

these are packets I captured with Wireshark, and you can see that the IP of CS and TS is obtained in 2491 and then tries to establish a new connection with CS 192.168.0.3.

I debugged the process of creating the database, and found that the IP obtained in MetadataUpdater is not 10.xxx.xxx.xxx, and finally I can locate the hostname obtained from InetSocketAddress in NettyServer cannot be accessed externally. I've also tried modifying 'coordinator.host', setting it to 10.xxx.xxx.xxx will cause the service to fail to start.

I also tried Deploying Local Cluster. Whether coordinator.host is set to localhost or 10.xxx.xxx.xxx, the IP registered to ZK is the private IP of my server, which my PC can't access.
I have not found a way to access Fluss outside of the same local area network.

@haishui126 Thanks for reporting... Yes, you can't access Fluss from an extern network.. Fluss will need to support advertised.listeners like kafka.. See more detail in this article