-
Notifications
You must be signed in to change notification settings - Fork 325
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPB 2690 #4098
Conversation
pidfile="/var/tmp/turnserver.pid" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was added only to prevent a warning
- /usr/bin/dumb-init | ||
- -- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't strictly know if this is needed, but we've seen that processes linger around after pod is killed, but weren't able to reproduce. Having an init gives additional guarantees and should prevent subprocesses from remaining after the main process has been killed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(were not able to reproduce - or actually didn't spend the time to try out the real previous configuration to reproduce it)
charts/coturn: support putting coturn into 'drain' mode when terminating pods, denying new incoming client connections. This speeds up graceful coturn restarts significantly. See related PR wireapp/coturn#15 and wireapp/coturn#12
drive-by fixes:
Checklist
changelog.d