wuchong opened a new issue, #2534: URL: https://github.com/apache/fluss/issues/2534
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Description [https://github.com/apache/fluss/issues/2272](https://github.com/apache/fluss/issues/2272) updates the behavior of the `local-cluster.sh` script to use the same hostname (or IP address) specified in the `bind.listeners` configuration in `server.yaml`, while still binding TabletServers to port `0` to avoid conflicts with the Coordinator’s fixed port. This change ensures that the entire local cluster can be uniformly accessed from remote clients when needed. We should update the documentation accordingly. Specifically, the warning note at the top of the **["Deploying Local Cluster"](https://fluss.apache.org/docs/next/install-deploy/deploying-local-cluster/)** page should be revised to explain how to make the local cluster accessible from external machines, something like: > **This setup deploys Fluss to a single machine only.** The Fluss endpoint will only be accessible locally (e.g. via `localhost`) by default. To allow external access to your local cluster, configure an externally reachable hostname or IP in the `bind.listeners` field of `server.yaml`. When set, all services—including TabletServers—will bind to that address, making their ports accessible remotely. > > If you require full control over network exposure or plan to run Fluss across multiple machines, we recommend using the **[Deploying Distributed Cluster](https://fluss.apache.org/docs/next/install-deploy/deploying-distributed-cluster/)** guide instead, which explains how to deploy each CoordinatorServer and TabletServer with explicitly configured, externally accessible hostnames and ports. ### Willingness to contribute - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
