Project

General

Profile

Bug #29258

Dynflow world gets shared across puma workers in production

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
Plugin integration
Target version:
-

Associated revisions

Revision 29fe60a8 (diff)
Added by Adam Ruzicka 9 months ago

Fixes #29258 - Initialize dynflow in puma workers

When running puma in clustered mode in production, Dynflow would get initialized
in the master process before workers were forked off and due to CoW the workers
would use the same world id.

With this commit we will eagerly initialize Dynflow only when running under
Passenger. When running under puma, we will initialize Dynflow in workers.

Co-Authored-By: Ewoud Kohl van Wijngaarden <>

Revision dad02244 (diff)
Added by Adam Ruzicka 9 months ago

Refs #29258 - Lazy initialize dynflow during rake tasks

which need executor

History

#1 Updated by The Foreman Bot 9 months ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/7487 added

#2 Updated by The Foreman Bot 9 months ago

  • Fixed in Releases 2.1.0 added

#3 Updated by Adam Ruzicka 9 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by The Foreman Bot 9 months ago

  • Pull request https://github.com/theforeman/foreman/pull/7490 added

#5 Updated by The Foreman Bot 7 months ago

  • Pull request https://github.com/theforeman/foreman/pull/7614 added

#6 Updated by The Foreman Bot 7 months ago

  • Pull request https://github.com/theforeman/foreman/pull/7615 added

#7 Updated by Tomer Brisker 7 months ago

  • Category set to Plugin integration
  • Fixed in Releases 1.24.3, 2.0.1 added

Also available in: Atom PDF