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.
During start up, our team has been getting:
In our testing we found that it took approx 2-4s for the sync container to not only be running, but for the rsync daemon to be listening on the desired port. The
start_container
method in rsync.rb seemed to handle most of these start delays with asleep 3
but if the rsync daemon is still not available after 3s, the initial sync is attempted anyway, resulting in the above error.The connection to the rsync daemon can be tested with the
--dry-run
flag. So I've attempted ahealth_check
method that will use this call to wait until rsync is listening on the desired port and container IP.This
health_check
method will wait until thersync --dry-run...
command returns a non empty string. It will only try 10times to prevent an infinite loop, and any issues syncing after that are handled normally by thesync
method.Thanks!