Project

General

Profile

Bug #31964

Sidekiq workers are configured to process queues sequentially

Added by Adam Ruzicka 7 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:

Description

the jobs in the "remote_execution" queue will only be processed only if the "default" queue is empty.

Associated revisions

Revision e2e5d355 (diff)
Added by Ewoud Kohl van Wijngaarden 6 months ago

Refs #31964 - Introduce foreman::to_symbolized_yaml

This function symbolizes keys in YAML which is typically what Foreman
config files use. This is hard to achieve with pure Puppet so a Ruby
function is used.

Revision 616f172d (diff)
Added by Ewoud Kohl van Wijngaarden 6 months ago

Fixes #31964 - Assign equal weight to sidekiq queues

The previous approach worker, but it made sidekiq default worker process all
items from the default queue before moving to remote execution queue. This
change adds equal weight to the queues, making sidekiq pick jobs from both.

History

#1 Updated by The Foreman Bot 7 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman/pull/919 added

#2 Updated by Ewoud Kohl van Wijngaarden 7 months ago

  • Triaged changed from No to Yes
  • Category set to Foreman modules

#3 Updated by The Foreman Bot 6 months ago

  • Pull request https://github.com/theforeman/puppet-foreman/pull/927 added

#4 Updated by The Foreman Bot 6 months ago

  • Fixed in Releases 2.5.0 added

#5 Updated by Ewoud Kohl van Wijngaarden 6 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF