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.

Sign up for GitHub

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

Jump to bottom

make pulpcore-(api|content) same priority as workers #934

Merged
merged 1 commit into from
Oct 9, 2024
Merged

make pulpcore-(api|content) same priority as workers #934

merged 1 commit into from
Oct 9, 2024
+2 −2

Commits on Oct 9, 2024

  1. make pulpcore-(api|content) same priority as workers 

    there is no good reason to have them at different priorities.
additionally, having them at 10 actually hurts as it's the same priority
as PostgreSQL which means the logs will be spammed by "connection
refused" if the DB is shut down while api/content are still in the
process of being shut-down (or booted up).

this does *not* fix the segfaults problem -- but at least makes the logs
a tad cleaner
    @evgeni
    evgeni committed Oct 9, 2024
    Configuration menu
    Copy the full SHA
    a463895 View commit details
    Browse the repository at this point in the history