DanielCarter-stack commented on issue #10569:
URL: https://github.com/apache/seatunnel/issues/10569#issuecomment-4011114750
<!-- code-pr-reviewer -->
Thanks for reporting this issue. Based on the logs and configuration, this
appears to be a **port configuration mismatch** rather than a code bug.
## Root Cause
The issue is in your docker-compose.yml. You're mixing host ports with
container ports:
```yaml
ports:
- 5802:5801 # Host 5802 -> Container 5801
environment:
- ST_DOCKER_MEMBER_LIST=st-master,st-worker1:5802,st-worker2:5803
```
Problems:
1. Workers listen on port **5802** inside the container (per
`config/hazelcast-worker.yaml`)
2. Your `ST_DOCKER_MEMBER_LIST` references `:5802/:5803`, which are the
**host-mapped ports**
3. In Docker overlay networks, containers must communicate using **internal
ports**
## Solution
Change `ST_DOCKER_MEMBER_LIST` to use service names with the **container
port (5801)**:
```yaml
environment:
- ST_DOCKER_MEMBER_LIST=st-master:5801,st-worker1:5801,st-worker2:5801
```
The port mappings (`5802:5801`, `5803:5801`) are only for external access.
Inter-container communication uses port 5801 internally.
Please try this corrected configuration and let us know if the issue
persists.
--
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]
