Skip to content

Conversation

@khk-globus
Copy link
Contributor

@khk-globus khk-globus commented Apr 30, 2025

This implements a restart-in-place mechanism via exec(). The logic serializes and re-establishes state:

  • The child processes do not lose their parent; the new endpoint instance maintains the exact same PID

  • In-flight audit records are protected, and the new instance sets up writing to the MEP file. A hot restart will be visible in the audit log file as the MEP shutting down and restarting.

  • A log record is emitted to the "normal" logs indicating that hot restart is happening

  • Until we have a proper MEP pid file, the only access to hot-restart an MEP is to send the process SIGHUP.

[sc-40933]

Type of change

  • New feature (non-breaking change that adds functionality)

khk-globus added a commit that referenced this pull request Apr 30, 2025
This implements a restart-in-place mechanism via `exec()`.  The logic
serializes and re-establishes state:

- The child processes do not lose their parent; the new endpoint instance
  maintains the exact same PID

- In flight audit records are protected, and the new instance setups writing to
  the MEP file.  A hot restart will be visible in the audit log file as the MEP
  shutting down and restarting.

- A log record is emitted to the "normal" logs indicating that hot restart is
  happening

- Until we have a proper MEP pid file, the only access to hot-restart an MEP is
  to send the process SIGHUP.

[sc-40933]
@khk-globus khk-globus force-pushed the sc-40933/implement_mep_hot_restart branch from a3b1a7b to 9b49818 Compare April 30, 2025 18:48
This implements a restart-in-place mechanism via `exec()`.  The logic
serializes and re-establishes state:

- The child processes do not lose their parent; the new endpoint instance
  maintains the exact same PID

- In-flight audit records are protected, and the new instance setups writing to
  the MEP file.  A hot restart will be visible in the audit log file as the MEP
  shutting down and restarting.

- A log record is emitted to the "normal" logs indicating that hot restart is
  happening

- Until we have a proper MEP pid file, the only access to hot-restart an MEP is
  to send the process SIGHUP.

[sc-40933]
@khk-globus khk-globus force-pushed the sc-40933/implement_mep_hot_restart branch from 9b49818 to c8cfdfb Compare April 30, 2025 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants