Skip to content
This repository has been archived by the owner on Mar 14, 2023. It is now read-only.

How to handle G2 soft off signal. #26

Open
axot opened this issue Mar 18, 2020 · 1 comment
Open

How to handle G2 soft off signal. #26

axot opened this issue Mar 18, 2020 · 1 comment

Comments

@axot
Copy link

axot commented Mar 18, 2020

We are testing how to use Preemptible VM in GKE with this project.
In the Preemptible VM document here said,

Compute Engine sends a preemption notice to the instance in the form of an ACPI G2 Soft Off signal. You can use a shutdown script to handle the preemption notice and complete cleanup actions before the instance stops.

In our test, if we do not block systemd to handle this signal, pod couldn't graceful shutdown.[1]
So my question is instead to monitor instance/preempted event, how about to handle G2 soft off signal, is this a better way to perform?

Thanks.

[1] https://raw.githubusercontent.com/axot/examples/daisaru11/nginx-stresstest/staging/nginx-metrics/disable-powerkey.yaml

@axot axot changed the title How to handling G2 soft off signal. How to handle G2 soft off signal. Mar 18, 2020
@axot
Copy link
Author

axot commented Apr 16, 2020

@mindprince I think this issue was discussed inside Google, I'm thinking about

  1. block G2 signal in OS side
  2. evict PODs using k8s-node-termination-handler
  3. shutdown OS to ensure all OS side processes could shutdown gracefully.

Any thoughts?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant