Many users failed to connect during peak hour, end user needs to try several times then can be connected successfully. customer has deployed three connectors, when issue occurs, high CPU and memory was found on some connectors.
The issue was caused by Connector Load balance issue, when issue occurs, three connectors are not load balanced, NGS forward all requests to one or two connectors, that caused high CPU and high memory. the current design of connector's load balance is calculated by network TTL, which may not stable enough.
A new algorithm of load balance was implemented in Citrix Daas, change the routing algorithm to Static Proximity in backend service.
Daas - many users failed to connect during peak hour