ic4y opened a new issue, #2210:
URL: https://github.com/apache/incubator-seatunnel/issues/2210

   ### Search before asking
   
   - [X] I had searched in the 
[feature](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22)
 and found no similar feature requirement.
   
   
   ### Description
   
   As shown below
   
   Use Hazelcast's NodeExtension to extend the implementation of the engine, 
relying on Hazelcast dynamic scaling, automatic master selection, and 
distributed memory.
   The gray part in the figure is hezalcast, and the blue part is ST-engine.
   
   
   job submit:
   The client submits a job to the ST-Service of the Master node, Job generates 
a physical execution plan Task in ST-Service and submits it to ST-Service of 
other nodes in the cluster for execution.
   Information such as its job status is maintained in Hazelcast's Imap 
(distributed storage).
   
   
   fault tolerance:
   The ST-Service instance is stateless (the state is stored in Hazelcast's 
distributed storage), so when the Master node hangs up. Hazelcast will 
automatically elect another node as the Master, and the ST-Service on this node 
will continue to provide services.
   
   <img width="791" alt="image" 
src="https://user-images.githubusercontent.com/83933160/179716975-b79b9a25-33b7-4d71-86da-8b696e12065d.png";>
   
   
   
   
   ### Usage Scenario
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to