[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1946: Elastic-Job task persistence

[GitBox <gi...@apache.org>]

TeslaCN commented on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-891566223


   > > ElasticJob doesn't rely on Database. Job configurations are persisted in the Registry Center. Quartz is used to trigger the job.
   > > Could you tell me something about your scenario?
   > 
   > Registry center refers to the zookeeper?
   > Two more questions about this zookeeper?
   > 
   > 1. How to re launch the crashed task?
   > 2. Why are some tasks executed by two instances and some by only one instance?
   >    ![image](https://user-images.githubusercontent.com/29774996/127444238-cf63bfe7-29a7-400a-81a0-da1f0bd2cbeb.png)
   
   ElasticJob is a SDK, you can make good use of it in your way. I wrote a demo about schedule jobs dynamically, you may refer to it.
   https://github.com/TeslaCN/flexijob/blob/master/src/main/java/icu/wwj/flexijob/internal/listener/NewJobListener.java


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org