Skip to content

Increase transientTimeout of boltdb to 2mimute#135

Open
coolljt0725 wants to merge 1 commit intodocker:masterfrom
coolljt0725:increase_timeout
Open

Increase transientTimeout of boltdb to 2mimute#135
coolljt0725 wants to merge 1 commit intodocker:masterfrom
coolljt0725:increase_timeout

Conversation

@coolljt0725
Copy link
Copy Markdown

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

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 coolljt0725 changed the title Increase transientTimeout of boltdb to 2m Increase transientTimeout of boltdb to 2mimute Aug 4, 2016
@thaJeztah
Copy link
Copy Markdown
Member

ping @abronan PTAL

@abronan
Copy link
Copy Markdown
Contributor

abronan commented Aug 11, 2016

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants