DanielCarter-stack commented on issue #10496: URL: https://github.com/apache/seatunnel/issues/10496#issuecomment-3901324938
<!-- code-pr-reviewer --> Based on the repository analysis, SeaTunnel defaults to port 5801 in both `config/hazelcast-client.yaml` and `deploy/kubernetes/seatunnel/conf/hazelcast-client.yaml`. The port 5701 behavior you're observing is Hazelcast's default when no port is specified in `cluster-members` addresses. Key points from the codebase: - `seatunnel-engine-common/src/main/java/org/apache/seatunnel/engine/common/config/ConfigProvider.java:99-120` shows client config loading via `ST_DOCKER_MEMBER_LIST` env var or YAML file - `seatunnel-starter/src/main/java/org/apache/seatunnel/core/starter/seatunnel/command/ClientExecuteCommand.java:102-105` confirms Local mode dynamically fetches the actual server port To troubleshoot, please verify: 1. What's the actual content inside the container at `/opt/seatunnel/config/hazelcast-client.yaml`? 2. Is the `ST_DOCKER_MEMBER_LIST` environment variable set (it overrides YAML config)? 3. Are your `cluster-members` entries explicitly specifying `:5801` (without port, Hazelcast defaults to 5701)? -- 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]
