Skip to content

Conversation

@anyasabo
Copy link
Contributor

Relates to #2259

Default the readiness timeout 3s, but allow the user to set an env var to override the timeout for clusters that are under load. Currently it is hardcoded so changing the timeout means you need to change the whole readiness probe

@anyasabo anyasabo added the >enhancement Enhancement of existing functionality label Dec 12, 2019
Copy link
Contributor

@charith-elastic charith-elastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@anyasabo anyasabo merged commit 97a29c1 into elastic:master Dec 13, 2019
@anyasabo anyasabo deleted the timeout branch December 13, 2019 15:04
#!/usr/bin/env bash
# Consider a node to be healthy if it responds to a simple GET on "/_cat/nodes?local"
CURL_TIMEOUT=3
CURL_TIMEOUT=${CURL_TIMEOUT:=3}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this env var name should be more explicit: READINESS_CURL_TIMEOUT

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

READINESS_PROBE_TIMEOUT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I'll open a new PR

@anyasabo anyasabo added the v1.0.0 label Jan 8, 2020
mjmbischoff pushed a commit to mjmbischoff/cloud-on-k8s that referenced this pull request Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>enhancement Enhancement of existing functionality v1.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants