Add association between Process and Jobs, and add a heartbeat to the Process record #999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connects to #831 / #985.
locked_by_id
andlocked_at
columns to Jobs which is updated when the job is executed with theGoodJob::Process.id
and then unset after executing.ProcessTracker
which is responsible for creating and destroyingGoodJob::Process
records when locks are taken, and also refreshing the record in the background on a regular cadence (a heartbeart)Goal here is to have all of the database migrations in place for the major GoodJob 4.0 release (#764) so that developers can safely opt into new behavior (like using row-level-locks+heartbeat instead of advisory locks)