New rhttpproxy configuration parameters to limit the number of connections per endpoint in a vc/esx

Products

• VMware vSphere ESXi

Issue/Introduction

Enabling vc admins to limit the number of connections per endpoint.

 
Few scenarios:

1. To disable this mechanism, set defaultMaxConnectionsPerEndpoint to 0
2. To change the percent of connections per endpoint, set connectionsPerEndpointPercentage to that value
3. To add specific handling for some endpoints use maxConnectionsPerEndpoint

In general you will not want to mix these in the same config. particularly,
defaultMaxConnectionsPerEndpoint = 0 with the rest is not meaningful.

you should choose between using defaultMaxConnectionsPerEndpoint equal to some value different than 0 OR using connectionsPerEndpointPercentage

The maxConnectionsPerEndpoint is always useful as it will take precedence over the others.

Symptoms:

In rhttpproxy config file , you may find below content under <proxy> element. If you don't find, you can manually add it.
  
 <!-- Default max number of connections per endpoint. 0 is unlimited.
        If maxConnections is not unlimited and defaultMaxConnectionsPerEndpoint
        is not set, then defaultMaxConnectionsPerEndpoint will be 80% of
        maxConnections. -->
  <!-- <defaultMaxConnectionsPerEndpoint>0</defaultMaxConnectionsPerEndpoint> -->

   <!-- Controls the percentage (default 80%) that
        defaultMaxConnectionsPerEndpoint will be from maxConnections. -->
   <!-- <connectionsPerEndpointPercentage>80</connectionsPerEndpointPercentage> -->

   <!-- Max number of connections per each endpoint entry.
        The format is a list of:
        <endpoint1> = <limit1>, <endpoint2> = <limit2>, ...
        For example:
        /endpoint1, /endpoint2=, /endpoint3 = 20, /endpoint4 = 0
        The limit for endpoint1 and endpoint 2 is defaultMaxConnectionsPerEndpoint.
        The limit for endpoint3 is 20 connections.
        endpoint4 is unlimited. -->
  <!-- <maxConnectionsPerEndpoint>/endpoint = 20</maxConnectionsPerEndpoint> -->
   

Environment

VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.7

Resolution

This issue is resolved in vSphere 6.5.0 U3r and 6.7.0 U3p