You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/07/27 13:58:04 UTC
[GitHub] [shardingsphere-elasticjob] Yenuo opened a new issue #1946: Elastic-Job task persistence
Yenuo opened a new issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946
1. Elastic-Job supports the persistence of scheduled tasks to the database. The next time you start the service, you can read the scheduled tasks from the database for scheduled execution. At present, elasticjob-Lite does not support this, but elasticjob-Lite supports the tracking and persistence of task events to the database. Is there a plan to implement this persistence to the database?
2. Elastic-Job inherits quartz. Why doesn't quartz's tasks persist to the database? The next time the service starts, you can call up all tasks in batch to continue to execute. Has elastic job removed this function?
--
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
[GitHub] [shardingsphere-elasticjob] Yenuo commented on issue #1946: Elastic-Job task persistence
Posted by GitBox <gi...@apache.org>.
Yenuo commented on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-888847844
> 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?
--
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
[GitHub] [shardingsphere-elasticjob] Yenuo commented on issue #1946: Elastic-Job task persistence
Posted by GitBox <gi...@apache.org>.
Yenuo commented on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-888845198
My appeal is that the service needs to be able to dynamically add and delete scheduled tasks, and can continue to execute the previously created scheduled tasks after the service is restarted.
Service refers to the dynamic management task implemented by job scheduling using elasticjob-Lite（ https://shardingsphere.apache.org/elasticjob/current/cn/quick-start/elasticjob-lite/ ）
--
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
[GitHub] [shardingsphere-elasticjob] Yenuo commented on issue #1946: Elastic-Job task persistence
Posted by GitBox <gi...@apache.org>.
Yenuo commented on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-887552482
In other words, after the service is restarted, how to pull up the tasks in zookeeper and execute scheduled tasks.
--
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
[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1946: Elastic-Job task persistence
Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-888829337
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?
--
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
[GitHub] [shardingsphere-elasticjob] Yenuo edited a comment on issue #1946: Elastic-Job task persistence
Posted by GitBox <gi...@apache.org>.
Yenuo edited a comment on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-888847844
> 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?
--
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
[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1946: Elastic-Job task persistence
Posted by 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?
> 
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
[GitHub] [shardingsphere-elasticjob] Yenuo commented on issue #1946: Elastic-Job task persistence
Posted by GitBox <gi...@apache.org>.
Yenuo commented on issue #1946:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1946#issuecomment-888778271
https://github.com/apache/shardingsphere-elasticjob/issues/706
The problem is the same as mine，How did you solve it？
--
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