Skip to content
This repository was archived by the owner on Feb 14, 2023. It is now read-only.

Fix #117 - Add longer health check timeout on register-buddy container#120

Open
nicko170 wants to merge 1 commit into
cloudfoundry:mainfrom
nicko170:main
Open

Fix #117 - Add longer health check timeout on register-buddy container#120
nicko170 wants to merge 1 commit into
cloudfoundry:mainfrom
nicko170:main

Conversation

@nicko170

Copy link
Copy Markdown

Australia is a loooong way away from hub.docker.com, which causes the register-buddy sidecar to constantly crash as seen in #117. Every request to /healthz calls the external API service before responding, and 1 second timeout is simply not enough time.

Adding a 3 second check timeout here fixes the issue, vs the default liveness check timeout of 1 second.

~ /usr/bin/time curl -ivs http://127.0.0.1:8889/healthz
*   Trying 127.0.0.1:8889...
* Connected to 127.0.0.1 (127.0.0.1) port 8889 (#0)
> GET /healthz HTTP/1.1
> Host: 127.0.0.1:8889
> User-Agent: curl/7.77.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Thu, 27 Jan 2022 04:37:56 GMT
Date: Thu, 27 Jan 2022 04:37:56 GMT
< Content-Length: 0
Content-Length: 0

<
* Connection #0 to host 127.0.0.1 left intact
        1.98 real         0.00 user         0.00 sys

@cf-gitbot

Copy link
Copy Markdown
Collaborator

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/181054922

The labels on this github issue will be updated when the story is started.

@bosh-admin-bot

Copy link
Copy Markdown

This pull request was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

@nicko170

Copy link
Copy Markdown
Author

Bump.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants