Alvenshi commented on issue #5830: URL: https://github.com/apache/seatunnel/issues/5830#issuecomment-1812010156
when i choose disrutor as the queue-type in seatunnel.yaml specific configuration:  then i run the class SeaTunnelEngineServerExample,and call rest api to submit a job ,so i can call the url of /hazelcast/rest/maps/running-job to get the job info,such as  and then i call the rest api to stop running job, the request url is /hazelcast/rest/maps/stop-job  but when i call the url of /hazelcast/rest/maps/running-job to get the job info  the status of job is canceling,not the end state of job but when i choose blockingqueue as the queue-type in seatunnel.yaml,repeat the above steps,i can see the status of job is canceled. so are there any problems when using disruptor as the queue type in seatunnel.yaml? -- 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]
