Describe the bug
Several times in GKE deployments, and Openshift, the dev-rethinkdb-proxy container has become disconnected from dev-rethinkdb-cluster and does not recover until the pod is manually recreated.
Disconnected from server "dev_rethinkdb_cluster_0"
To Reproduce
To reproduce deploy to GKE/Openshift and wait. It has taken weeks to happen.
Expected behavior
rethinkdb-proxy to recover should it lose connection to rethinkdb-cluster
Screenshots
Additional context
Have seen this same issue caused by rethinkdb-cluster restarting.
In these cases though there isn't any visible issue with rethinkdb-cluster.
Describe the bug Several times in GKE deployments, and Openshift, the
dev-rethinkdb-proxycontainer has become disconnected fromdev-rethinkdb-clusterand does not recover until the pod is manually recreated.Your environment rethinkdb-proxy: chart:
rethinkdb-1.1.4image:codylundquist/helm-rethinkdb-cluster:0.1.0rethinkdb-cluster: chart:rethinkdb-1.1.4image:codylundquist/helm-rethinkdb-cluster:0.1.0To Reproduce To reproduce deploy to GKE/Openshift and wait. It has taken weeks to happen.
Expected behavior rethinkdb-proxy to recover should it lose connection to rethinkdb-cluster
Screenshots
Additional context Have seen this same issue caused by rethinkdb-cluster restarting. In these cases though there isn't any visible issue with rethinkdb-cluster.