Advice on "persist hash" load balancing

Hi Roger,

 

 

Glad I could help. That's a common trap.

 

 

Without OneConnect enabled, I can't explain whatever connection pooling you saw.

 

 

However, OneConnect with either mask is viable in production, and either will be more efficient than none at all, since handshake overhead for your servers will be reduced.

 

 

With OneConnect configured with the default mask of 0.0.0.0, any idle serverside connection may be re-used for any new clientside request, significantly reducing the number of serverside connections.

 

 

However, re-used serverside connections retain the source IP of the original client, which results in some very misleading server log entries unless you are also SNATing all connections.

 

 

Without SNAT, OneConnect with a host mask (255.255.255.255) keeps the source address info in the server logs consistent with reality.

 

 

If you're already SNATing, the 0.0.0.0 mask will result in more efficient connection pooling.

 

 

HTH

 

/deb