You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, so I've been trying to use gnmi-gateway within a k8s cluster and deploy it with clustering using zookeeper.
For this configuration, everything is working fine:
As you can see here, the gateway acquires the lock for each target, syncs with them and starts sending requests and overall the deployment works fine:
Then, for testing purposes, I manually scaled up the gnmi-gateway deployment to two replicas, and started having issues with the second replica of the deployment, while the first one keeps running fine:
And then the pod enters in a crashloop.
I haven't figured out if I am missing some configuration when I traced the error and I was wondering what could be causing that panic.
The text was updated successfully, but these errors were encountered:
stefan-chivu
changed the title
Please use a meaningful title
Using multiple instances within k8s deployment triggers panic
Feb 23, 2022
stefan-chivu
changed the title
Using multiple instances within k8s deployment triggers panic
Using multiple instances within k8s deployment with zookeeper triggers panic and crashes pod
Feb 23, 2022
Hi, so I've been trying to use gnmi-gateway within a k8s cluster and deploy it with clustering using zookeeper.
For this configuration, everything is working fine:
As you can see here, the gateway acquires the lock for each target, syncs with them and starts sending requests and overall the deployment works fine:
Then, for testing purposes, I manually scaled up the gnmi-gateway deployment to two replicas, and started having issues with the second replica of the deployment, while the first one keeps running fine:
And then the pod enters in a crashloop.
I haven't figured out if I am missing some configuration when I traced the error and I was wondering what could be causing that panic.
The text was updated successfully, but these errors were encountered: