Forum Discussion
Gateway Cluster only works one
Yes, that is one of the worst case scenarios, when a cluster member thinks it is ready to serve requests but it isn't. The load balancer will give it jobs which will then fail. In that case it is better to disable the cluster member and visit it with a clue-by-four.
The other worst case scenario is when the proxy is down. No proxy = no gateway.
Super UserThe gateway cluster will work if at least one member is available. Of course for Business Continuity you want to have at least two.
The "principal" or "anchor" designation of a cluster member is garbage. It has no technical meaning. If you want to change the role you can use the "take over/restore" option on another cluster member to kick the anchor off its throne.
Make sure "Distribute load across cluster members" is enabled.
Thank you very much for the answer and the clarifications, so what is happening is that when the "main" or "anchor" is without the VPN the entire update gives an error, but if I disable it it ends up working. And I enabled the "Distribute load across cluster members" option.
- lbendlin
Yes, that is one of the worst case scenarios, when a cluster member thinks it is ready to serve requests but it isn't. The load balancer will give it jobs which will then fail. In that case it is better to disable the cluster member and visit it with a clue-by-four.
The other worst case scenario is when the proxy is down. No proxy = no gateway.
I understand, so there is no solution, the way is to disable and enable it manually when you need to use it