ccoffline opened a new issue, #10496:
URL: https://github.com/apache/seatunnel/issues/10496
`hazelcast-client.yaml`
```yaml
hazelcast-client:
cluster-name: seatunnel
properties:
hazelcast.logging.type: log4j2
connection-strategy:
connection-retry:
cluster-connect-timeout-millis: 3000
network:
cluster-members:
- *.*.*.*:5801
# I have tried both with port and without. Still doesn't work.
- *.*.*.*
```
`hazelcast.yaml`
```yaml
hazelcast:
cluster-name: seatunnel
network:
port:
auto-increment: false
port: 5801
rest-api:
enabled: true
endpoint-groups:
CLUSTER_WRITE:
enabled: true
DATA:
enabled: true
join:
tcp-ip:
enabled: true
member-list:
- *.*.*.*
```
`seatunnel.yaml`
```yaml
seatunnel:
engine:
classloader-cache-mode: true
history-job-expire-minutes: 1440
backup-count: 1
queue-type: blockingqueue
print-execution-info-interval: 60
print-job-metrics-info-interval: 60
slot-service:
dynamic-slot: true
checkpoint:
interval: 10000
timeout: 60000
storage:
type: hdfs
max-retained: 3
plugin-config:
***
telemetry:
metric:
enabled: false
logs:
scheduled-deletion-enable: true
http:
enable-http: true
port: 5800
enable-dynamic-port: false
```
```bash
docker exec -it seatunnel /opt/seatunnel/bin/seatunnel.sh -l
2026-02-14 14:08:17,814 INFO [c.h.i.c.AbstractConfigLocator ] [main] -
Loading configuration '/opt/seatunnel/config/seatunnel.yaml' from System
property 'seatunnel.config'
2026-02-14 14:08:17,817 INFO [c.h.i.c.AbstractConfigLocator ] [main] -
Using configuration file at /opt/seatunnel/config/seatunnel.yaml
2026-02-14 14:08:17,819 INFO [o.a.s.e.c.c.SeaTunnelConfig ] [main] -
seatunnel.home is /opt/seatunnel
2026-02-14 14:08:17,903 INFO [amlSeaTunnelDomConfigProcessor] [main] -
Dynamic slot is enabled, the schedule strategy is set to REJECT
2026-02-14 14:08:17,903 INFO [c.h.i.c.AbstractConfigLocator ] [main] -
Loading configuration '/opt/seatunnel/config/hazelcast.yaml' from System
property 'hazelcast.config'
2026-02-14 14:08:17,903 INFO [c.h.i.c.AbstractConfigLocator ] [main] -
Using configuration file at /opt/seatunnel/config/hazelcast.yaml
2026-02-14 14:08:18,162 INFO [c.h.i.c.AbstractConfigLocator ] [main] -
Loading configuration '/opt/seatunnel/config/hazelcast-client.yaml' from System
property 'hazelcast.client.config'
2026-02-14 14:08:18,162 INFO [c.h.i.c.AbstractConfigLocator ] [main] -
Using configuration file at /opt/seatunnel/config/hazelcast-client.yaml
2026-02-14 14:08:18,449 INFO [.c.i.s.ClientInvocationService] [main] -
hz.client_1 [seatunnel] [5.1] Running with 2 response threads, dynamic=true
2026-02-14 14:08:18,510 INFO [c.h.c.LifecycleService ] [main] -
hz.client_1 [seatunnel] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is
STARTING
2026-02-14 14:08:18,510 INFO [c.h.c.LifecycleService ] [main] -
hz.client_1 [seatunnel] [5.1] HazelcastClient 5.1 (20220228 - 21f20e7) is
STARTED
2026-02-14 14:08:18,532 INFO [.c.i.c.ClientConnectionManager] [main] -
hz.client_1 [seatunnel] [5.1] Trying to connect to cluster: seatunnel
2026-02-14 14:08:18,534 INFO [.c.i.c.ClientConnectionManager] [main] -
hz.client_1 [seatunnel] [5.1] Trying to connect to [***]:5701
2026-02-14 14:08:18,542 WARN [.c.i.c.ClientConnectionManager] [main] -
hz.client_1 [seatunnel] [5.1] Exception during initial connection to
[***]:5701: com.hazelcast.core.HazelcastException: java.io.IOException:
Connection refused to address /***:5701
2026-02-14 14:08:18,542 INFO [.c.i.c.ClientConnectionManager] [main] -
hz.client_1 [seatunnel] [5.1] Trying to connect to [***]:5701
2026-02-14 14:08:18,543 WARN [.c.i.c.ClientConnectionManager] [main] -
hz.client_1 [seatunnel] [5.1] Exception during initial connection to
[***]:5701: com.hazelcast.core.HazelcastException: java.io.IOException:
Connection refused to address /***:5701
```
I know that hazelcast use 5701 in default but I have config everywhere to be
5801.
--
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]
