EricJoy2048 commented on issue #5444: URL: https://github.com/apache/seatunnel/issues/5444#issuecomment-1715342210
> I had solved this problem ,the reason： the job still use 2.3.2 seatunnel，but the cluster had upgrade to 2.3.3. check the log like this : Sep 11, PM com.hazelcast.internal.config.AbstractConfigLocator INFO: Loading configuration '/opt/apache-seatunnel-2.3.2/config/seatunnel.yaml' from System property 'seatunnel.config' Yes, you are right. -- 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]
