GangLiCN commented on issue #8227: URL: https://github.com/apache/seatunnel/issues/8227#issuecomment-2527495047
> > > Hi, can you attach your `hazelcast.yaml` config. And when start failed, is 5801 port used by other application? > > > > > > More information: > > > > 1. All seatunnel configuration files is original files, I didn't modify any of them ; > > 2. 5801 port was not used by other applications when I tried to execute "seatunnel.cmd". > > > > I think that the real issue is: On Windows, there are some issues on handling seatunnel server startup or there is no code logical to handle seatunnel server startup, which looks like more serious. > > 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 hazelcast.heartbeat.failuredetector.type: phi-accrual hazelcast.heartbeat.interval.seconds: 2 hazelcast.max.no.heartbeat.seconds: 180 hazelcast.heartbeat.phiaccrual.failuredetector.threshold: 10 hazelcast.heartbeat.phiaccrual.failuredetector.sample.size: 200 hazelcast.heartbeat.phiaccrual.failuredetector.min.std.dev.millis: 100 > > try to update `auto-increment` to `true`. let's see it can work or not. I tried it, unfortunately Seatunnel server still could not startup, same error as before. -- 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: commits-unsubscr...@seatunnel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
