Increase transientTimeout of boltdb to 2mimute #135
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
During docker stress test, there are a lot of timeout errors on update libnetwork object to store. `ERRO[0137] docker: Error response from daemon: failed to update store for object type *libnetwork.endpoint: timeout. error=exit status 125` I think we should increase the timeout to 2m because 2m is also the timeout of container starting timeout of docker. Signed-off-by: Lei Jitang <leijitang@huawei.com>
coolljt0725
changed the title
|
ping @abronan PTAL |
|
I don't know if this is the right approach to bump the default transient timeout to fix the tests (hitting the error mostly because of limited resources on the CI), imho the field should be configurable with libnetwork and using a custom value for testing. But I'm not familiar with how libnetwork configures boltdb. ping @sanimej as this impacts boltdb and libnetwork. |
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.
During docker stress test, there are a lot of
timeout errors on update libnetwork object to store.
ERRO[0137] docker: Error response from daemon: failed to update store for object type *libnetwork.endpoint: timeout. error=exit status 125I think we should increase the timeout to 2m because 2m is also the
timeout of container starting timeout of docker.
Signed-off-by: Lei Jitang leijitang@huawei.com