-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[DocDB][Pg cron] Intermittent Failure of Cron Job Execution in Stress Test Runs Despite Latest Fixes on Master #24658
Labels
2024.2_blocker
2024.2.0_blocker
2024.2.1_blocker
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
priority/high
High Priority
qa_stress
Bugs identified via Stress automation
QA
QA filed bugs
Comments
shishir2001-yb
added
area/ysql
Yugabyte SQL (YSQL)
priority/high
High Priority
QA
QA filed bugs
status/awaiting-triage
Issue awaiting triage
qa_stress
Bugs identified via Stress automation
2024.2_blocker
labels
Oct 28, 2024
shishir2001-yb
added
area/docdb
YugabyteDB core features
and removed
area/ysql
Yugabyte SQL (YSQL)
labels
Oct 28, 2024
shishir2001-yb
changed the title
[YSQL][Pg cron] Intermittent Failure of Cron Job Execution in Stress Test Runs Despite Latest Fixes on Master
[DocDB][Pg cron] Intermittent Failure of Cron Job Execution in Stress Test Runs Despite Latest Fixes on Master
Oct 28, 2024
yugabyte-ci
added
2024.2.1_blocker
and removed
status/awaiting-triage
Issue awaiting triage
labels
Oct 28, 2024
|
hari90
added a commit
that referenced
this issue
Oct 31, 2024
Summary: Original commit: d07daec / D39552 Switch pg_cron to normal using normal `SIGTERM` and `SIGQUIT` handlers. In an attempt to fix stuck pg_cron workers the handler of `SIGTERM` was changed to `quickdie` 4b4c201/D37591. But in `quickdie` mode postgres does not invoke `ReportBackgroundWorkerExit` which signals the parent process when its child backend exits. This causes pg_cron launcher to get stuck in `WaitForBackgroundWorkerShutdown`. With 111b65d/D39207 the issues with pg shutdown have been addressed and it is safe to now switch to the normal SIGTERM behavior which makes the background workers `die` in a clean manner. #24706 tracks the issue where in yb `ReportBackgroundWorkerExit` is not called when the backend has a non graceful exit. Fixes #24658 Jira: DB-13724 Test Plan: PgCronTest, DeactivateRunningJob Reviewers: telgersma Reviewed By: telgersma Subscribers: yql, ybase Differential Revision: https://phorge.dev.yugabyte.com/D39617
hari90
added a commit
that referenced
this issue
Oct 31, 2024
Summary: Original commit: d07daec / D39552 Switch pg_cron to normal using normal `SIGTERM` and `SIGQUIT` handlers. In an attempt to fix stuck pg_cron workers the handler of `SIGTERM` was changed to `quickdie` 4b4c201/D37591. But in `quickdie` mode postgres does not invoke `ReportBackgroundWorkerExit` which signals the parent process when its child backend exits. This causes pg_cron launcher to get stuck in `WaitForBackgroundWorkerShutdown`. With 111b65d/D39207 the issues with pg shutdown have been addressed and it is safe to now switch to the normal SIGTERM behavior which makes the background workers `die` in a clean manner. #24706 tracks the issue where in yb `ReportBackgroundWorkerExit` is not called when the backend has a non graceful exit. Fixes #24658 Jira: DB-13724 Test Plan: PgCronTest, DeactivateRunningJob Reviewers: telgersma Reviewed By: telgersma Subscribers: yql, ybase Differential Revision: https://phorge.dev.yugabyte.com/D39621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2024.2_blocker
2024.2.0_blocker
2024.2.1_blocker
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
priority/high
High Priority
qa_stress
Bugs identified via Stress automation
QA
QA filed bugs
Jira Link: DB-13724
Description
Version: 2.25.0.0-b214
Logs: Added in jira
Additionally, the count of executed jobs remains constant, suggesting that no new cron jobs are being triggered.
Test description
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: