Bug 735087
Summary: | Non-unique job names breaks clustered Pinsetter. | ||
---|---|---|---|
Product: | [Community] Candlepin | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | candlepin | Assignee: | Jesus M. Rodriguez <jesusr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | John Sefler <jsefler> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 0.5 | CC: | jesusr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-07-17 13:04:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brenton Leanhardt
2011-09-01 12:24:08 UTC
Any word on this? fixed in master by 96cd75214f5699151f8567b13e5ac51264ac6c05 If quartz is in clustered mode, we shouldn't schedule any jobs. Doing so will cause a primary key violation on the second Candlepin node. The primary key for the table is: trigger name + trigger group. At first I believed it was that we weren't using unique enough names. The name collision was a red herring, the real problem is we don't want to create new jobs when in clustered mode. We now check to see if quartz is in clustered mode, and if there are any jobs already scheduled from another node. If not, we proceed to schedule the jobs as normal. Otherwise, we skip initialization of the jobs and join the existing cluster. Added getClassName(String) to Util. Updated unit tests. Marking all community bugs modified or beyong as closed. |