Skip to content

Commit

Permalink
make pulpcore-(api|content) same priority as workers
Browse files Browse the repository at this point in the history
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
  • Loading branch information
evgeni committed Oct 9, 2024
1 parent d2121cf commit a463895
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions definitions/features/pulpcore.rb
Original file line number Diff line number Diff line change
Expand Up @@ -68,8 +68,8 @@ def config_files

def self.pulpcore_common_services
[
ForemanMaintain::Utils.system_service('pulpcore-api', 10, :socket => 'pulpcore-api'),
ForemanMaintain::Utils.system_service('pulpcore-content', 10, :socket => 'pulpcore-content'),
ForemanMaintain::Utils.system_service('pulpcore-api', 20, :socket => 'pulpcore-api'),
ForemanMaintain::Utils.system_service('pulpcore-content', 20, :socket => 'pulpcore-content'),
]
end
end

0 comments on commit a463895

Please sign in to comment.