• Sales: 1-800-961-2888
  • Support: 1-800-961-4454

Preventing Server Overload


One of the ways you can prevent a server from becoming overloaded is to use the Connection Throttling feature of Cloud Load Balancers. Connection throttling basically imposes limits on the number of connections per IP address. This feature helps prevent malicious or abusive traffic to your server and its installed applications.

Configure Connection Throttling

Note: This procedure assumes you're working with an existing load balancer. If you don't have a load balancer yet, create one now using these instructions: Configuring a Load Balancer.

To configure connection throttling:

  1. Click Load Balancers at the top of the Control Panel.
  2. Click on Actions cog next to your load balancer and select Edit Connection Throttling from the menu.

The following pop-over appears:

Connection Throttling Pop-over

  1. Enter a value for each option, and then click Save Connection Throttling. The Connection Throttling options are descibed below.

Setting Connection Throttling Options

When configuring connection throttling, you can specify the following options:

Max. Connections

Specifies the maximum number of simultaneous connections to allow from a single IP address. You can specify a value between 1 and 100000.

Threshold

Specifies the level of simultaneous connections from any IP address at which to apply the throttling restrictions defined by the Limit to and Timeframe fields (see below). You can specify a value between 1 and 1000.

Limit to

Specifies the maximum number of new connections allowed from a single IP address in the defined Timeframe (see Timeframe below). Specify a value between 1 and 100000.

Timeframe

Specifies the interval (in seconds) at which the limit for new connections is assessed once the Threshold is reached. Specify a value between 1 and 3600.

The following field is updated automatically based on your settings for the Threshold, Limit to, and Timeframe fields:

Summary

Describes the results that will be produced by your settings for Threshold, Limit to, and Timeframe.

For example, if you enter 25 simultaneous connections from any IP for the Threshold, 25 new connections for Limit to, and 5 seconds for the Timeframe, after 25 simultaneous connections from any IP, your load balancer would only allow a maximum of 25 new connections for a single IP address every 5 seconds.

 



© 2011-2013 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER

6 Comments

The image included in this article has nothing to do with the terms described below it. One of them needs an urgent update.

I'm not sure what you mean, German. Could you be more specific about the inconsistency?

Sorry Jered, I was not notified of the comment.
If you read the config options that appear in the image you'll see that the explanation below happens to be for other terms options. The image seems to be the real deal, and the explanation obsolete.

Aha, thank you for the clarification. I see it now. Looks like the content for the first-gen control panel was copied over but not updated for the newer control panel. We'll get that fixed soon, then.

Hi German,

We've updated this article so that the labels in explanation match the labels in the UI. Thanks for bringing this to our attention!

When the load balancer decides that it needs to throttle (due to actual traffic being above what's been configured using the directions on this page), what exactly happens? One assumes that the settings are per-server, and that the balancer will attempt to use another server. But if all servers are being throttled, what happens? Does the balancer send back a HTTP 429 ("too many requests") response?

Add new comment