Skip to content

process_launcher: the sub-processes are stopped one after the other, up to 5 seconds each #459

Closed

Description

@njoubert-cleverage

Description

ProcessLauncherTask::finalize() and killProcesses() stop the running sub-processes one after the other with stop(5): each one gets SIGTERM and up to 5 seconds before SIGKILL, the next one only after.

With 8 sub-processes ignoring or slowly handling SIGTERM, stopping them takes up to 40 seconds, longer than the grace period of docker stop (10 s) or of Kubernetes (30 s): the parent process is killed in the middle of finalize(), its execution stays started (cleverage/ui-process-bundle), and the remaining sub-processes are left as orphans.

Proposed fix

Send SIGTERM to all of them, wait for them together up to the timeout, then SIGKILL the ones still running.

Requirements

  • Documentation updates
    • Reference
    • Cookbooks
    • Changelog
  • Unit tests

Breaking changes

None.

Activity

  1. added 4 commits that reference this issue on Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions