Cannot set triggers with the same trigger name for different tasks under different scheduling instances

michaelklishin / quartz-mongodb

A MongoDB-based store for the Quartz scheduler. This fork strives to be as feature complete as possible. Originally by MuleSoft.

Other

247 stars 199 forks source link

Cannot set triggers with the same trigger name for different tasks under different scheduling instances #183

Closed jasonhuxinlei closed 4 years ago

jasonhuxinlei commented 4 years ago

Task 1: The scheduling instance name is testScheduler1 Task 2: The scheduling instance name is testScheduler2 Task names, task group names, trigger names, and trigger group names for task one and task two are the same Task 1: Task 2: I started task one first and saw the normal execution; then I started task two and found that an error occurred

michaelklishin commented 4 years ago

I'd consider a PR that makes it possible to support multiple scheduler instances. However, this will be a breaking change as far as the data we store in MongoDB goes, and I don't consider this use case a priority for this or any other job store.