Swarm.Tracker - fix start_pid_remotely retrying rapidly
#129
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
|
I've seen this also happen to us just today in our production cluster. There haven't been any deploys in like 3 weeks, and everything ran smooth until this happened. When this happened we got ~11M logs in 2 hours of this retrying and not being able to fix itself. Restarted the pods and then everything got back to normal We are running 2 pods on a k8s cluster. Lib is a dependency of https://github.com/commanded/commanded-swarm-registry We are using swarm lib 3.4.0 |
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.
Noticed a lot of this message in our logs:
It seems to happen randomly, but I think this will fix it