-
Notifications
You must be signed in to change notification settings - Fork 19
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
forward port workarround for queue populator batch getting stuck #2544
Conversation
Hello kerkesni,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
... and 2 files with indirect coverage changes
@@ Coverage Diff @@
## development/8.7 #2544 +/- ##
===================================================
- Coverage 69.56% 69.50% -0.06%
===================================================
Files 194 194
Lines 12792 12803 +11
===================================================
Hits 8899 8899
- Misses 3883 3894 +11
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. |
f605ea3
to
85f130b
Compare
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command:
Alternatively, the |
85f130b
to
5a630a0
Compare
00b882b
to
9c67ba8
Compare
9c67ba8
to
29b5481
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
d1b659e
to
29b5481
Compare
lib/queuePopulator/LogReader.js
Outdated
this.log.error('queue populator batch timeout', { | ||
logStats: batchState.logStats, | ||
}); | ||
process.emit('SIGTERM'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we really "crash" ?
could we not just fail healthcheck? (may not be supported at the moment in s3c, but will need to anyway...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as i know, S3C (precisely supervisord) doesn't support restarting a process on healthcheck failure.
I added logic for failing the healthcheck, but i'm still keeping the crashing behaviour.
f5fcc9b
to
fa9f680
Compare
fa9f680
to
9d1905c
Compare
Issue: BB-526
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue BB-526. Goodbye kerkesni. |
7.x fix was not forward ported to avoid introducing memory leaks into the code. Instead of just unblocking the next batch processing call and leaving the stuck one alive, now we shutdown the whole process.
7.x fix commit: dfcc2f5
Issue: BB-526