-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Add timeout for I/O waitgroups #3361
Conversation
Closes containerd#3286 This and a combination of a couple Docker changes are needed to fully resolve the issue on the Docker side. However, this ensures that after processes exit, we still leave some time for the I/O to fully flush before closing. Without this timeout, the delete methods would block forever. Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Build succeeded.
|
Codecov Report
@@ Coverage Diff @@
## master #3361 +/- ##
==========================================
- Coverage 49.01% 45.08% -3.94%
==========================================
Files 102 113 +11
Lines 9886 12542 +2656
==========================================
+ Hits 4846 5654 +808
- Misses 4193 6032 +1839
- Partials 847 856 +9
Continue to review full report at Codecov.
|
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.
LGTM
This is the second part to containerd/containerd#3361 and will help process delete not block forever when the process exists but the I/O was inherited by a subprocess that lives on. Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
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.
LGTM
This is the second part to containerd/containerd#3361 and will help process delete not block forever when the process exists but the I/O was inherited by a subprocess that lives on. Signed-off-by: Michael Crosby <crosbymichael@gmail.com> Upstream-commit: b5f28865efebb14c66d5580dfa7bf0634b5e3241 Component: engine
This is the second part to containerd/containerd#3361 and will help process delete not block forever when the process exists but the I/O was inherited by a subprocess that lives on. Signed-off-by: Michael Crosby <crosbymichael@gmail.com> (cherry picked from commit b5f2886) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This is the second part to containerd/containerd#3361 and will help process delete not block forever when the process exists but the I/O was inherited by a subprocess that lives on. Signed-off-by: Michael Crosby <crosbymichael@gmail.com> (cherry picked from commit b5f28865efebb14c66d5580dfa7bf0634b5e3241) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 34b31d0ee06d1fcbf9b94b34b130fbeaf65a83a8 Component: engine
Backport for containerd#3361 This and a combination of a couple Docker changes are needed to fully resolve the issue on the Docker side. However, this ensures that after processes exit, we still leave some time for the I/O to fully flush before closing. Without this timeout, the delete methods would block forever. Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
This is the second part to containerd/containerd#3361 and will help process delete not block forever when the process exists but the I/O was inherited by a subprocess that lives on. Signed-off-by: Michael Crosby <crosbymichael@gmail.com> Signed-off-by: zach <Zachary.Joyner@linux.com>
Closes #3286
This and a combination of a couple Docker changes are needed to fully
resolve the issue on the Docker side. However, this ensures that after
processes exit, we still leave some time for the I/O to fully flush
before closing. Without this timeout, the delete methods would block
forever.
Signed-off-by: Michael Crosby crosbymichael@gmail.com