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.

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

Already on GitHub? Sign in to your account

Soft shutdown not working #2435

Closed
corverroos opened this issue Jul 14, 2023 · 0 comments
Closed

Soft shutdown not working #2435

corverroos opened this issue Jul 14, 2023 · 0 comments
Labels
bug Something isn't working protocol Protocol Team tickets

Comments

@corverroos
Copy link
Contributor

馃悶 Bug Report

Description

When stopping the charon docker container it doesn't always do a proper clean soft shutdown. Docker needs to send a sig kill command after 10s for the container to exit.

This is probably related to long running vapi proxy event requests that are not force closed on context cancel.

Proposed Solution

Refactor the proxy in vapi to cancel proxied requests when the application context is closed.

@corverroos corverroos added the bug Something isn't working label Jul 14, 2023
@github-actions github-actions bot added the protocol Protocol Team tickets label Jul 14, 2023
obol-bulldozer bot pushed a commit that referenced this issue Aug 7, 2023
Fixes soft shutdown by cancelling long running proxied requests.

This is because long lived connections are not interrupted by `http.Server.Shutdown`:
```
// Shutdown gracefully shuts down the server without interrupting any
// active connections. Shutdown works by first closing all open
// listeners, then closing all idle connections, and then waiting
// indefinitely for connections to return to idle and then shut down...
```

category: bug
ticket: #2435
gsora pushed a commit that referenced this issue Aug 9, 2023
Fixes soft shutdown by cancelling long running proxied requests.

This is because long lived connections are not interrupted by `http.Server.Shutdown`:
```
// Shutdown gracefully shuts down the server without interrupting any
// active connections. Shutdown works by first closing all open
// listeners, then closing all idle connections, and then waiting
// indefinitely for connections to return to idle and then shut down...
```

category: bug
ticket: #2435
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working protocol Protocol Team tickets
Projects
None yet
Development

No branches or pull requests

1 participant