How to implement the task scheduler service using Quartz.net for multiple servers?

I want to implement a task scheduler using Quartz.Net in a WCF service that have the following requirement:

  • must be a WCF service.
  • hosted on multiple servers in multiple locations.
  • runs only once, although the scheduler service runs on several servers at a specific time.
  • History can be maintained through any database.
  • can perform any kind of work, such as an .exe file, image file, a specific task, any command, sql queries, etc.
  • I'm just trying to figure out if quartz scheduler can be used on multiple servers, all pointing to the same database.
  • Also my main motivation for this is the failure mechanism, as well as the spread of the load.

I have a little knowledge about Quartz.Net and I created on a test sample, and I am also looking for more detailed information on how Quartz.net actually runs on the system, how the memory of Quartz.net users, etc.

+2
source share
1 answer

With the exception of the wcf part, all of your problems described above can be solved with Quartz.Net. Just install the service on all the necessary servers. Configure them as clustered and list them in the same database. This covers most of your items.

You can create a WCF shell if you want to communicate directly with Quartz.Net, since it only supports remote access.

You can write a job listener to register task history.

Running executable files is supported out of the box. For other types of tasks, you will need to create your own task.

+3
source

All Articles