Connections from SAS sessions to a SAS® Metadata Server cluster manager do not follow connection redirects


When a connection is made to a clustered SAS Metadata Server manager host, the server responds with a redirect that asks the client to disconnect and connect to one of the worker nodes.

When a SAS session (such as a Workspace Server, Batch Server, Grid Server, and so on) receives this redirect, the SAS session reconnects to the same manager host rather than the worker node. Then, the manager handles the requests normally.

Although this behavior does not cause a failure, it can place an undesirable processing workload on the cluster's manager node.

In the logs for a SAS Metadata Server cluster manager, the SAS Metadata server log indicates this behavior: a redirect is followed immediately by a new connection from the same client, and no such connection logged in the redirect target server's log.

2026-08-24T19:45:36,201 INFO  [00688090] :sasdemo - New client connection (56229) accepted from server port 8561 for trusted SAS peer user sasdemo.  Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.0.0.1]:49697 for APPNAME=SAS.
2026-08-24T19:45:36,201 INFO  [00688090] :sasdemo - Request made to cluster SASMeta - Logical Metadata Server (A5Z40WOV.AX000001).
2026-08-24T19:45:36,201 INFO  [00688090] :sasdemo - Redirect client in cluster SASMeta - Logical Metadata Server (A5Z40WOV.AX000001) to server SASMeta - Metadata Server Node 3 (A5Z40WOV.AZ000013) at metanod-2.example.com:8561.
2026-08-24T19:45:36,202 INFO  [00688090] :sas - Client connection 56229 for user sasdemo closed.
2026-08-24T19:45:36,306 INFO  [00688094] :sasdemo - New client connection (56227) accepted from server port 8561 for trusted SAS peer user sasdemo.  Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.0.0.1]:49698 for APPNAME=SAS.
2026-08-24T19:45:36,566 INFO  [00688105] 56227:sas - Client connection 56227 for user sasdemo closed.

This behavior could also occur in connections from Object Spawner or Connect Spawners to a Metadata cluster or connections to Object Spawners in a load-balancing configuration.