Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

changes for handling mux child processes when mux dies #301

Merged
merged 5 commits into from
Jan 10, 2023
Merged

changes for handling mux child processes when mux dies #301

merged 5 commits into from
Jan 10, 2023

Conversation

rasamala83
Copy link
Collaborator

@rasamala83 rasamala83 commented Dec 22, 2022 •
edited
Loading

Added Code in MUX to handle Zombie/defunct process issues in case MUX died due to any panic errors.

Verified following cases:

  1. If MUX killed through SIGKILL(9) then process can't handle this signal, only parent watchdog can handle child death through SIGCHLD signal. In this case watchdog will make sure to kill all grand childs(workers) and release resource but we can't avoid zombie process issue in this case.
  2. Raise panic in process and make sure it releases system resource

@ModEtchFill
Copy link
Contributor

All tests pass combining go/container-job runs 311 and 313

@rasamala83 rasamala83 merged commit 01fbf24 into paypal:master Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@venkatsridhar95 venkatsridhar95 venkatsridhar95 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@rasamala83 @ModEtchFill @venkatsridhar95