Closed EntainAustralia closed 5 months ago
This might be a bug, gNMIc is trying to list all leases with a context that already reached its deadline. The 0.1 seconds is an internal retry timer, changing it won't solve this problem. Can you share which version of gNMI you are running ?
Seeing this on 0.36.2, This also could be a misconfiguration due to the limited documentation around the k8s locker. We configured the k8s locker based on a comment in https://github.com/karimra/gnmic/issues/560#issuecomment-1102234193
We are on version 0.36.2
version : 0.36.2
commit : a7844a6d
date : 2024-03-05T20:10:26Z
gitURL : https://github.com/openconfig/gnmic
docs : https://gnmic.openconfig.net
The solution was to make sure the ENV variables were configured correctly. These were removed originally because they were not documented or explained in any way.
- name: GNMIC_CLUSTERING_INSTANCE_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: GNMIC_CLUSTERING_SERVICE_ADDRESS
value: "$(GNMIC_CLUSTERING_INSTANCE_NAME).gnmic-svc.gnmic.svc.cluster.local"
The ENV variables follow a naming pattern explained here: https://gnmic.openconfig.net/user_guide/configuration_env/#configuration-file-to-environment-variables-mapping
GNMIC_CLUSTERING_INSTANCE_NAME=XXX
and GNMIC_CLUSTERING_SERVICE_ADDRESS=YYY
are equivalent to:
clustering:
instance-name: XXX
service-address: YYY
One of our two targets receives a context deadline error very quickly (every 0.1 second). Can this rate be reduced somewhere or can we change something else to fix it?
Config
Logs