liunaijie commented on issue #6171: URL: https://github.com/apache/seatunnel/issues/6171#issuecomment-1999198515
> > yes, when you run `seatunnel-cluster.sh -d` command it will start the server with 5801 port. when you run `-e local` command again, it will start the server again. so you will got error > > thanks, can i change the `hazelcast-client.yaml` or `hazelcast.yaml` config to comply run local and sever both? yes, `hazelcast.yaml` is used on server side. `hezalcast-client.yaml` is used on client side. you need both update the files. also please use same `cluster-name`. it will verify the ip, port and cluster-name, all match can be join together. By the way, if you has run `./bin/seatunnl-cluster.sh -d`, then the server cluster is startup, you can use `./bin/seatunnel.sh -c <config_file>` command without `-e local` parameter to submit the job, it will be ok. and if you run `./bin/seatunnel.sh -c <config file> -e local`. it will start the server node in this process and the client join the server created in this process. -- 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]
