1151025 - Increase docker timeout from 60 seconds to 120 seconds

Status: RESOLVED DUPLICATE of bug 1173528

(Developer Services :: General, task)

Description

[Ben Kero [:bkero]]

I am having a problem wherein during the running of the bmoweb entry point, the docker-control script will timeout waiting for the httpd daemon to start. I've found this issue to persist across my desktop and laptop.

I've bumped the timeout locally from 60 seconds to 120 seconds, which fixes the problem 100% of the time.

Comment 1

[Ben Kero [:bkero]]

Attachment: MozReview Request: bz://1151025/bkero

/r/6619 - Bug 1151025: vcttesting: update docker timeout to 120 seconds

Pull down this commit:

hg pull -r 5be4dec94e5aa01c452d80d8d9a3293ad63a5358 https://reviewboard-hg.mozilla.org/version-control-tools/

Comment 2

[Ben Kero [:bkero]]

Comment on attachment 8588125 [details]
MozReview Request: bz://1151025/bkero

/r/6619 - Bug 1151025: vcttesting: update docker timeout to 120 seconds

Pull down this commit:

hg pull -r 5be4dec94e5aa01c452d80d8d9a3293ad63a5358 https://reviewboard-hg.mozilla.org/version-control-tools/

Comment 3

[Gregory Szorc [:gps]]

Comment on attachment 8588125 [details]
MozReview Request: bz://1151025/bkero

https://reviewboard.mozilla.org/r/6617/#review5539

No modern machine should be hitting a 60s timeout. I'm curious why your machine is super slow. Magnetic disks? Not enough memory?

Most consumers of this API should only be experiencing maybe 5s of lag before return. I'd feel much better if we changed the default timeout on the client side than as the default value in the function itself. Look for the function call somewhere in docker.py.

Comment 4

[Ben Kero [:bkero]]

I'm hitting this on my desktop. It's running on native Linux (not a VM). It has a 3.4GHz Ivy Bridge quad core with 32GB RAM and an SSD that will do 415MB/sec sequential read and 260MB/sec sequential writes. I doubt very much that it's a hardware problem.

I also experience it on my Laptop with a 2.6GHz Sandy Bridge with 12GB RAM and a similar SSD.

I can go look for another place to go patch this if you don't feel comfortable adjusting the default timeout. This timeout only occurs for me during operations on the bmoweb host.

Comment 5

[Ben Kero [:bkero]]

Comment on attachment 8588125 [details]
MozReview Request: bz://1151025/bkero

/r/6619 - Bug 1151025: vcttesting: update docker timeout to 120 seconds
/r/6699 - Bug 1151025: Increase wait_for_http timeout in the one instance it is used

Pull down these commits:

hg pull -r fd8d927f83926229da0e30965d152aca4d53abb1 https://reviewboard-hg.mozilla.org/version-control-tools/

Comment 6

[Gregory Szorc [:gps]]

Comment on attachment 8588125 [details]
MozReview Request: bz://1151025/bkero

These two patches need to be folded together (drop the first patch) and rebased since they have been bitrotted.

I'm still curious why your machine takes so long to start BMO...

Comment 8

[Ben Kero [:bkero]]

Attachment: MozReview Request: Bug 1151025: Increase wait_for_http timeout in the one instance it is used

Comment 9

[Ben Kero [:bkero]]

Attachment: MozReview Request: Bug 1151025: vcttesting: update docker timeout to 120 seconds