watch: support multiple containers for tar implementation#10860
Merged
Conversation
milas
requested review from
StefanScherer,
glours,
laurazard,
ndeloof,
nicksieger and
ulyssessouza
and removed request for
a team
August 1, 2023 21:25
Support services with scale > 1 for the tar watch sync. Add a "lossy" multi-writer specific to pipes that writes the tar data to each `io.PipeWriter`, which is connected to `stdin` for the `tar` process being exec'd in the container. The data is written serially to each writer. This could be adjusted to do concurrent writes but that will rapidly increase the I/O load, so is not done here - in general, 99% of the time you'll be developing (and thus using watch/sync) with a single replica of a service. If a write fails, the corresponding `io.PipeWriter` is removed from the active set and closed with an error. This means that a single container copy failing won't stop writes to the others that are succeeding. Of course, they will be in an inconsistent state afterwards still, but that's a different problem. Signed-off-by: Milas Bowman <[email protected]>
glours
approved these changes
Aug 2, 2023
glours
left a comment
glours
left a comment
Contributor
There was a problem hiding this comment.
LGTM, thanks for the test 👍
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## v2 #10860 +/- ##
==========================================
- Coverage 59.88% 58.29% -1.60%
==========================================
Files 118 120 +2
Lines 10064 10377 +313
==========================================
+ Hits 6027 6049 +22
- Misses 3440 3728 +288
- Partials 597 600 +3
☔ View full report in Codecov by Sentry. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What I did
Support services with scale > 1 for the tar watch sync.
Add a "lossy" multi-writer specific to pipes that writes the tar data to each
io.PipeWriter, which is connected tostdinfor thetarprocess being exec'd in the container.The data is written serially to each writer. This could be adjusted to do concurrent writes but that will rapidly increase the I/O load, so is not done here - in general, 99% of the time you'll be developing (and thus using watch/sync) with a single replica of a service.
If a write fails, the corresponding
io.PipeWriteris removed from the active set and closed with an error.This means that a single container copy failing won't stop writes to the others that are succeeding. Of course, they will be in an inconsistent state afterwards still, but that's a different problem.
(not mandatory) A picture of a cute animal, if possible in relation to what you did
