wolgod opened a new issue, #1090:
URL: https://github.com/apache/apisix-ingress-controller/issues/1090
### Issue description
2022-06-20T20:09:55+08:00 warn apisix/cluster.go:482 failed to
check health for cluster default: dial tcp: i/o timeout, will retry
### Environment
- your apisix-ingress-controller version (output of
apisix-ingress-controller version --long):1.4.1
- your Kubernetes cluster version (output of kubectl version): k8s 1.20.11
cni kube-ovn
- if you run apisix-ingress-controller in Bare-metal environment, also show
your OS version (uname -a):
### Minimal test code / Steps to reproduce
1. when Ingress Controller run，in console sometimes will print failed to
check health for cluster default: dial tcp: i/o timeout, will retry， at set
intervals，the Ingress Controller will give up leader and all controllers will
exit
### Actual result
the Ingress controller running normal
### Error log
[GIN] 2022/06/20 - 20:05:53 | 200 | 79.995µs | 10.168.136.32 | GET
"/healthz"
[GIN] 2022/06/20 - 20:05:55 | 200 | 70.659µs | 10.168.136.32 | GET
"/healthz"
2022-06-20T20:05:56+08:00 warn apisix/cluster.go:482 failed to
check health for cluster default: dial tcp: i/o timeout, will retry
[GIN] 2022/06/20 - 20:06:03 | 200 | 66.2µs | 10.168.136.32 | GET
"/healthz"
2022-06-20T20:06:04+08:00 warn apisix/cluster.go:482 failed to
check health for cluster default: dial tcp: i/o timeout, will retry
2022-06-20T20:06:04+08:00 warn ingress/controller.go:692
failed to check health for default cluster: timed out waiting for the
condition, give up leader
2022-06-20T20:06:04+08:00 info ingress/endpoint.go:84 endpoints
controller exited
2022-06-20T20:06:04+08:00 info ingress/ingress.go:71 ingress
controller exited
2022-06-20T20:06:04+08:00 info ingress/namespace.go:82 namespace
controller exited
2022-06-20T20:06:04+08:00 info ingress/pod.go:56 pod
controller exited
2022-06-20T20:06:04+08:00 info ingress/apisix_consumer.go:67
ApisixConsumer controller exited
2022-06-20T20:06:04+08:00 info ingress/apisix_upstream.go:71
ApisixUpstream controller exited
2022-06-20T20:06:04+08:00 info ingress/apisix_route.go:74
ApisixRoute controller exited
2022-06-20T20:06:04+08:00 info ingress/apisix_pluginconfig.go:71
ApisixPluginConfig controller exited
2022-06-20T20:06:04+08:00 info ingress/apisix_tls.go:71
ApisixTls controller exited
2022-06-20T20:06:04+08:00 info ingress/secret.go:76 secret
controller exited
2022-06-20T20:06:04+08:00 info ingress/apisix_cluster_config.go:69
ApisixClusterConfig controller exited
2022-06-20T20:06:04+08:00 info ingress/controller.go:372
controller now is running as a candidate {"namespace": "apisix-test",
"pod": "apisix-ingress-1-apisix-ingress-controller-5b989b6cd9-nht59"}
I0620 20:06:04.618665 1 leaderelection.go:248] attempting to acquire
leader lease apisix-test/ingress-apisix-leader...
2022-06-20T20:06:04+08:00 info ingress/controller.go:320
LeaderElection {"message":
"apisix-ingress-1-apisix-ingress-controller-5b989b6cd9-nht59 became leader",
"event_type": "Normal"}
I0620 20:06:04.626745 1 leaderelection.go:258] successfully acquired
lease apisix-test/ingress-apisix-leader
2022-06-20T20:06:04+08:00 info ingress/controller.go:406
controller tries to leading ... {"namespace": "apisix-test", "pod":
"apisix-ingress-1-apisix-ingress-controller-5b989b6cd9-nht59"}
2022-06-20T20:06:04+08:00 warn apisix/cluster.go:332 waiting
cluster default to ready, it may takes a while
2022-06-20T20:06:04+08:00 info apisix/cluster.go:160 syncing
cache {"cluster": "default"}
2022-06-20T20:06:04+08:00 info apisix/cluster.go:372 syncing
schema {"cluster": "default"}
### Expected result
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
