You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2022/03/25 11:28:00 UTC
[jira] [Updated] (YUNIKORN-1153) Admission controller: first health check should be delayed
[ https://issues.apache.org/jira/browse/YUNIKORN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko updated YUNIKORN-1153:
-----------------------------------
Description:
When deploying Yunikorn locally, I often see the first health check failing:
{noformat}
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m12s default-scheduler Successfully assigned default/yunikorn-admission-controller-78c775cfd9-6pp8d to minikube
Normal Pulled 3m12s kubelet Container image "apache/yunikorn:admission-latest" already present on machine
Normal Created 3m12s kubelet Created container yunikorn-admission-controller
Normal Started 3m11s kubelet Started container yunikorn-admission-controller
Warning Unhealthy 2m52s (x2 over 3m2s) kubelet Startup probe failed: Get "https://192.168.49.2:9089/health": dial tcp 192.168.49.2:9089: connect: connection refused
{noformat}
We need to add some {{initialDelaySeconds}} to wait with the first probe. 10-15 seconds is probably a good value.
was:
When deploying Yunikorn locally, I often see the first health check failing:
{noformat}
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m12s default-scheduler Successfully assigned default/yunikorn-admission-controller-78c775cfd9-6pp8d to minikube
Normal Pulled 3m12s kubelet Container image "apache/yunikorn:admission-latest" already present on machine
Normal Created 3m12s kubelet Created container yunikorn-admission-controller
Normal Started 3m11s kubelet Started container yunikorn-admission-controller
Warning Unhealthy 2m52s (x2 over 3m2s) kubelet Startup probe failed: Get "https://192.168.49.2:9089/health": dial tcp 192.168.49.2:9089: connect: connection refused
{noformat}
We need add some {{initialDelaySeconds}} to wait with the first probe. 10-15 seconds is probably a good value.
> Admission controller: first health check should be delayed
> ----------------------------------------------------------
>
> Key: YUNIKORN-1153
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1153
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Peter Bacsko
> Priority: Minor
>
> When deploying Yunikorn locally, I often see the first health check failing:
> {noformat}
> Events:
> Type Reason Age From Message
> ---- ------ ---- ---- -------
> Normal Scheduled 3m12s default-scheduler Successfully assigned default/yunikorn-admission-controller-78c775cfd9-6pp8d to minikube
> Normal Pulled 3m12s kubelet Container image "apache/yunikorn:admission-latest" already present on machine
> Normal Created 3m12s kubelet Created container yunikorn-admission-controller
> Normal Started 3m11s kubelet Started container yunikorn-admission-controller
> Warning Unhealthy 2m52s (x2 over 3m2s) kubelet Startup probe failed: Get "https://192.168.49.2:9089/health": dial tcp 192.168.49.2:9089: connect: connection refused
> {noformat}
> We need to add some {{initialDelaySeconds}} to wait with the first probe. 10-15 seconds is probably a good value.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org