Our master tiebreaker node went offline and was not recoverable and the host has been destroyed. I have added a new master/tie breaker node and migrated the logging-metrics and admin-console-elasticserach clusters to the new master/tie breaker node.
The security cluster however will not let go of the association to the older master/tie breaker node and thinks that the security cluster if offline. (See message below)
My question is, how do I let the security cluster know that the old master node is dead and that it should use the new master node when the cluster thinks that it is offline?
{"ok":false,"message":"The requested cluster is currently unavailable"}