Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(postgres): jobs may never get processed if no workers hear the initial announcement #138

Merged
merged 1 commit into from
Jan 25, 2025

Conversation

acaloiaro
Copy link
Owner

No description provided.

@acaloiaro acaloiaro force-pushed the fix-unprocessed-past-due-jobs branch 2 times, most recently from 2e890c4 to f50ab3e Compare January 25, 2025 20:43
@acaloiaro acaloiaro changed the title feat: throttle error reporting when pending jobs fetch is in a tight loop fix(postgres): jobs may never get processed if no workers hear the initial announcement Jan 25, 2025
@acaloiaro acaloiaro force-pushed the fix-unprocessed-past-due-jobs branch from f50ab3e to fc6c165 Compare January 25, 2025 20:51
…itial announcement

When jobs are inserted into the 'neoq_jobs', the `announce_job` trigger announces the job to
listeners of the job's queue. However, if no workers are available to receive the announcement,
or the announcement is somehow lost, it meant those jobs were marooned on the queue.

This fix adds a periodic check for post-due pending jobs to ensure that a neoq restart is
not necessary to catch marooned, overdue jobs.
@acaloiaro acaloiaro force-pushed the fix-unprocessed-past-due-jobs branch from fc6c165 to 553ff5e Compare January 25, 2025 20:56
@acaloiaro acaloiaro merged commit 3b3a7fe into main Jan 25, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant