Load balancing the requests the Cloud Manager sends to the Developer Portal

You can balance the load of requests sent from the Cloud Manager to the Developer Portal

Load balancing requests from the CMC

The Cloud Manager accepts only a single IP address for the SSH requests that it sends to the Developer Portal to, so you must use a load balancer in TCP mode to front a cluster of Developer Portal machines if you want to ensure that the request from the Cloud Manager always finds an active cluster member. You can load balance an SSH connection in TCP mode as though you are load balancing an HTTPS pass through connection in TCP mode. The load balancer has no knowledge of the messages being exchanged, but does a basic health check to ensure that each node is healthy. Nodes that do not accept the connection are temporarily removed from the load balancer's target list.

Queue system

Each cluster has a cluster-wide queue, that the following actions go into:
  • Add site
  • Add language to a site
  • Delete site
  • Upgrade site
  • Update site
The site queue is always processed in order of priority. The priority is any non-add_language tasks in the order they came into the queue, and then any add_language tasks in the order they came into the queue.