Your sas-svi-alert service might fail to fail over to an available node under the following conditions:

• Your SAS Viya environment is configured with a high availability (HA) setup for RabbitMQ across multiple nodes.
• You shut down one of the nodes or one of the nodes becomes unavailable.

In this scenario, the service might have a status of not ready because it continues to try to connect to a node that is no longer available. The log might show that the service is trying to connect to an unavailable node. For example, in the log entry below, the “rabbitmq.node1.sas.com” host name represents a node that is unavailable:

In this scenario, the failover fails due to enablement of some of the old RabbitMQ queues that do not support platform failover.

To resolve the issue, use the following commands to disable those queues and restart the sas-svi-alert service and RabbitMQ nodes, as needed, to confirm the service failover is working:

Operating System and Release Information