fdb-kubernetes-operator
fdb-kubernetes-operator copied to clipboard
EmptyMonitorConf is flaky
What happened?
When using the EmptyMonitorConf it can happen that a cluster actually doesn't shutdown all processes and it's stuck in this state. We have to investigate why this is happening and fix the underlying issue.
What did you expect to happen?
EmptyMonitorConf should reliably shutdown all processes for the FDB cluster.
How can we reproduce it (as minimally and precisely as possible)?
Create a cluster and set the EmptyMonitorConf setting to true.
Anything else we need to know?
FDB Kubernetes operator
$ kubectl fdb version
# paste output here
v1.1.1
Kubernetes version
$ kubectl version
# paste output here