Bug #31964: Sidekiq workers are configured to process queues sequentially - Installer - Foreman

Bug #31964

Sidekiq workers are configured to process queues sequentially

Added by Adam Ruzicka about 2 years ago. Updated almost 2 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Adam Ruzicka

Category:

Foreman modules

Target version:

Difficulty:

Triaged:

Yes

Bugzilla link:

1932700

Pull request:

https://github.com/theforeman/puppet-foreman/pull/927, https://github.com/theforeman/puppet-foreman/pull/919

Fixed in Releases:

Foreman - 2.5.0

Found in Releases:

Red Hat JIRA:

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 almost 2 years 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 almost 2 years 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.