-
Notifications
You must be signed in to change notification settings - Fork 29
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
Fixes #33446 - Allow configuring Pulpcore worker timeout #230
Fixes #33446 - Allow configuring Pulpcore worker timeout #230
Conversation
eff37b8
to
826b3e7
Compare
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 noted in the offline chat: I'd keep init.pp small and rather add more instructions to README.md
about how to use diffsettings
.
This change implements the WORKER_TTL setting which lets Pulp decide how long to wait for a worker to respond before considering it gone and cleaning up it's database and re-assiging work.
826b3e7
to
bffd1bd
Compare
bffd1bd
to
3679d54
Compare
force pushing to trigger CI |
3679d54
to
3273438
Compare
@ekohl thank you for the feedback, I updated with the requested changes. While the tests passed for me locally, for some reason CI has not run on my recent pushes. Any idea why that is? |
When I opened issues I saw:
That's kind of weird. I guess they optimize the cronjobs on idle repos (which probably makes sense) but for us it's also the PR testing. I've enabled it now, but I'll take it up with GH. |
@ekohl thanks! any other feedback on this PR or do you think we are good to go? |
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.
No, I wanted to wait for CI to run.
No description provided.