matianhe3 commented on issue #6171: URL: https://github.com/apache/seatunnel/issues/6171#issuecomment-1960784240
> Perhaps it has to do with the contents of the configuration files in the config folder. For example, port: 5801 > > ```yaml > hazelcast-client: > cluster-name: seatunnel > properties: > hazelcast.logging.type: log4j2 > connection-strategy: > connection-retry: > cluster-connect-timeout-millis: 3000 > network: > cluster-members: > - localhost:5801 > ``` > > ``` > hazelcast: > cluster-name: seatunnel > network: > rest-api: > enabled: true > endpoint-groups: > CLUSTER_WRITE: > enabled: true > DATA: > enabled: true > join: > tcp-ip: > enabled: true > member-list: > - localhost > port: > auto-increment: false > port: 5801 > properties: > hazelcast.invocation.max.retry.count: 20 > hazelcast.tcp.join.port.try.count: 30 > hazelcast.logging.type: log4j2 > hazelcast.operation.generic.thread.count: 50 > ``` not this problem, same as you, when `seatunnel-cluster.sh -d` is running, `seatunnel.sh -m local` can not run. -- 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]
