Kill stuck fuse processes #152
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kill stuck fuse processes if they don't exit after timeout. Sometimes we observe s3fs processes being stuck even if the volumen is not a mountpoint anymore. As of now the pod would then be stuck forever in terminating state as we would only run in timeout and kubelet will retry to unmount in a loop Now we just kill the process if we run into the timeout Signed-off-by: Benjamin Isinger <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kill stuck fuse processes if they don't exit after timeout.
Sometimes we observe s3fs processes being stuck even if the volumen is not a mountpoint anymore.
As of now the pod would then be stuck forever in terminating state as we would only run in timeout and kubelet will retry to unmount in a loop
Now we just kill the process if we run into the timeout
Signed-off-by: Benjamin Isinger [email protected]