akalittle opened a new issue, #1273:
URL: https://github.com/apache/apisix-ingress-controller/issues/1273
### Issue description
```
2022-08-25T17:19:05+08:00 info ingress/ingress.go:121 use
configuration
{
"cert_file": "/etc/webhook/certs/cert.pem",
"key_file": "/etc/webhook/certs/key.pem",
"log_level": "info",
"log_output": "stderr",
"http_listen": ":8080",
"https_listen": ":8443",
"ingress_publish_service": ""
}
2022-08-25T17:19:05+08:00 warn api/server.go:75 failed to load
x509 key pair, will not start admission server {"Error": "open
/etc/webhook/certs/cert.pem: no such file or directory", "CertFilePath":
"/etc/webhook/certs/cert.pem", "KeyFilePath": "/etc/webhook/certs/key.pem"}
I0825 17:19:05.923522 1 leaderelection.go:248] attempting to acquire
leader lease apisix-istio/ingress-apisix-leader...
2022-08-25T17:19:05+08:00 info ingress/controller.go:320
LeaderElection {"message": "apisix-istio-ingress-controller-576d79598d-7mht8
became leader", "event_type": "Normal"}
I0825 17:19:05.940413 1 leaderelection.go:258] successfully acquired
lease apisix-istio/ingress-apisix-leader
2022-08-25T17:19:05+08:00 info ingress/controller.go:406
controller tries to leading ... {"namespace": "apisix-istio", "pod":
"apisix-istio-ingress-controller-576d79598d-7mht8"}
2022-08-25T17:19:05+08:00 warn ingress/controller.go:358 found a
new leader apisix-istio-ingress-controller-576d79598d-7mht8
2022-08-25T17:19:06+08:00 warn apisix/cluster.go:332 waiting cluster
default to ready, it may takes a while
2022-08-25T17:19:06+08:00 info apisix/cluster.go:372 syncing schema
{"cluster": "default"}
2022-08-25T17:19:06+08:00 info apisix/cluster.go:160 syncing cache
{"cluster": "default"}
2022-08-25T17:19:06+08:00 info apisix/cluster.go:164 cache synced
{"cost_time": "86.538102ms", "cluster": "default"}
2022-08-25T17:19:06+08:00 warn apisix/cluster.go:343 cluster default
now is ready, cost time 86.939563ms
[GIN] 2022/08/25 - 17:19:06 | 200 | 133.637µs | 127.0.0.6 | GET
"/healthz"
I0825 17:19:07.122781 1 request.go:665] Waited for 1.000344968s due to
client-side throttling, not priority and fairness, request:
GET:https://oneipaddress:443/apis/apisix.apache.org/v2beta3/namespaces/gcp-auth-proxy/apisixroutes
[GIN] 2022/08/25 - 17:19:08 | 200 | 3.251979ms | 127.0.0.6 | GET
"/metrics"
[GIN] 2022/08/25 - 17:19:11 | 200 | 59.305µs | 127.0.0.6 | GET
"/healthz"
[GIN] 2022/08/25 - 17:19:11 | 200 | 45.57µs | 127.0.0.6 | GET
"/healthz"
2022-08-25T17:19:14+08:00 info ingress/controller.go:546
controller now is running as leader {"namespace": "apisix-istio", "pod":
"apisix-istio-ingress-controller-576d79598d-7mht8"}
2022-08-25T17:19:14+08:00 info ingress/apisix_pluginconfig.go:57
ApisixPluginConfig controller started
2022-08-25T17:19:14+08:00 info ingress/ingress.go:59 ingress
controller started
2022-08-25T17:19:14+08:00 info ingress/namespace.go:71 namespace
controller started
2022-08-25T17:19:14+08:00 info ingress/pod.go:47 pod controller
started
2022-08-25T17:19:14+08:00 info ingress/endpoint.go:57 endpoints
controller started
2022-08-25T17:19:14+08:00 info ingress/apisix_upstream.go:58
ApisixUpstream controller started
2022-08-25T17:19:14+08:00 info ingress/apisix_tls.go:58
ApisixTls controller started
2022-08-25T17:19:14+08:00 info ingress/apisix_cluster_config.go:57
ApisixClusterConfig controller started
2022-08-25T17:19:14+08:00 info ingress/apisix_route.go:60
ApisixRoute controller started
2022-08-25T17:19:14+08:00 info ingress/secret.go:62 secret
controller started
2022-08-25T17:19:14+08:00 info ingress/apisix_consumer.go:56
ApisixConsumer controller started
```
After I delete the whole directory of apisix in etcd, but after I restart
the apisix-ingress-controller, the old data come back to etcd.
I'm quite curious about this log :`Waited for 1.000344968s due to
client-side throttling, not priority and fairness, request:
GET:https://oneipaddress:443/apis/apisix.apache.org/v2beta3/namespaces/gcp-auth-proxy/apisixroutes`
``
So how does it reload the data back ?
### Environment
apache/apisix:2.15.0-alpine
apache/apisix-ingress-controller:1.4.1
docker.io/bitnami/etcd:3.5.4-debian-11-r14
Kubernetes cluster version:
Client Version: v1.24.0
Kustomize Version: v4.5.4
Server Version: v1.21.12-gke.2200
--
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]
