Forum Discussion

mfkk531_168091's avatar
mfkk531_168091
Icon for Nimbostratus rankNimbostratus
Feb 05, 2015

Best Load Balancing Method to use with Session Cookie Persistence?

Hi All, I have VS with cookie persistence and RR lb method. I'm using a http profile but not onceconnect (as yet) I'm running into a situation where the server team is reporting that apache server sessions are way off 100 on first one and 500 on second one I'm about to add oneconnect profile to this VS , but wanted to confirm LB method. Should I leave it at RR? Will activating oneconnect help with my situation?

 

Any response much appreciated

 

6 Replies

  • shaggy's avatar
    shaggy
    Icon for Nimbostratus rankNimbostratus

    try using a non-rr lb method like least-connections (member). that may help even out current-connection levels to pool members. however, keep in mind that persistence will always cause uneven load to pool members

     

  • JD1's avatar
    JD1
    Icon for Altostratus rankAltostratus

    Hi Fasahat,

     

    Are you using these servers in multiple pools? Are you using any fallback persistence method?

     

    Perhaps consider using a load balancing method that takes into account the performance of your back end servers (observed,fastest,predictive), or even least connections based on node (if node is used multiple pools).

     

    If OneConnect was enabled, I wouldn't expect it to affect your load balancing, just the communication LTM->Backend.

     

    Also check to true up the results your server teams are telling you with the persistence statistics... Statistics > Module Statistics > Local Traffic > Persistent Records.

     

    Do you see 100 versus 500 persistence records for the nodes affected?

     

    Do the pool(s) statistics reflect the results or information from the server teams, in respect of current connections?

     

    Just some suggestions of what I'd look at initially.

     

    I suppose you could be unlucky in that one server had a lot of users who've closed their browser and others continued usage (if cookie persistence isn't set to expire until session end).

     

  • Implementing one-connect should reduce the load on the F5 when initiating a 3 way handshake to servers. (basically, it will reuse idle connections). Frequency and availability of which is also dependent on its profile settings.

     

    As shaggy also pointed out, least connections member would be ideal.

     

  • Thanks for your response JD Q - Are you using these servers in multiple pools? Are you using any fallback persistence method? A - No - these 2 nodes are only used in this 1 pool; No fallback persistence

     

    Q - Do you see 100 versus 500 persistence records for the nodes affected? A - No, I can't find a single entry for these Pool members or the pool name in persistence records, even though the pool stats show total 22 conn (6 and 16)

     

    Q - Do the pool(s) statistics reflect the results or information from the server teams, in respect of current connections? A - Nope, I see total current conn in pool - 22 (16 and 6). Total Connections are 10.4M (5.1M and 5.3M)

     

  • Thanks Nikhil & shaggy I will implement these 2 changes Activate OneConnect Change to Least Conn (member) I will report back once we test the outcome.

     

    • trx's avatar
      trx

      Hello mfgkk531, How did you config changes go? I'm experiencing a similar issue. Curious to know which config worked best for you when trying to evenly distribute traffic to pool nodes evenly when using a cookie persistence method.

       

      Let me know.

       

      Thanks.