Forum Discussion

Bryan_A's avatar
Bryan_A
Icon for Altostratus rankAltostratus
Nov 10, 2014

Connection limits with persistence

I'm trying to understand how connection limits work, especially with persistence (cookie based) enabled. Lets say I have a pool member with a connection limit of 50 defined for the member (not node), and in my browser session I have persistence to this member via cookie persistence. Lets say that the number of active connections to this member reaches 50. What happens to the next connection from me if the of active connections doesn't drop below the limit?

 

a. Connection is dropped and error returned to client b. Connection is sent to another pool member that has not exceeded its connection limit c. something else (if so what?)

 

Thank you.

 

application delivery
deployment
LTM

2 Replies

Sort By
  • rob_carr's avatar
    rob_carr
    Icon for Cirrostratus rankCirrostratus
    Nov 10, 2014

    Hey Bryan,

     

    Based on " target="_blank">Solution 9849, I think that the 51st connection will get a) LB'd to another pool member, provided one is available and not at it's connection limit or b) get a TCP-RST if no other pool member is available. Of course, this behavior could be modified by the TCP queuing options in 11.5.x and the 'Override Connection Limit' option of the Cookie Persistence profile.

     

  • Bryan_A's avatar
    Bryan_A
    Icon for Altostratus rankAltostratus
    Nov 10, 2014

    Hi Robert,

     

    Thanks. After reading the article you referenced, it does seem to indicate that it would attempt to send it to another pool member. I'll try to give it an actual test soon to confirm.