Urmi Mustafi created GOBBLIN-1875:
-------------------------------------
Summary: Create Unique Trigger identifiers
Key: GOBBLIN-1875
URL: https://issues.apache.org/jira/browse/GOBBLIN-1875
Project: Apache Gobblin
Issue Type: Bug
Components: gobblin-service
Reporter: Urmi Mustafi
Assignee: Abhishek Tiwari
We are seeing the following errors when trying to schedule reminders for
Multi-active scheduler after losing lease acquisition:
{{Unable to store Trigger with name: '...' and group: '...' because one already
exists with this identification}}
The Quartz scheduler allows multiple unique triggers mapping to one job in a
N:1 relation, but this requires the trigger having a unique identifier
associated with it. When we create triggers, we were previously using only the
job name and group to identify the trigger so we're unable to add additional
triggers for the same job. The trigger key is only used internally by the
Quartz scheduler, so it is safe to manipulate by adding a random number to
identify the trigger. We also don't expect more than a handful of triggers
associated with a job, so an int 0 to 1000 will be sufficient to uniquely
identify the trigger.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
