Forum Discussion
Jason_Hook_4092
Nimbostratus
NimbostratusPERSIST at the pool level only
I have a single VIP that will have two types of users. I don't want to define URLs for both so I'd like to use the PERSIST functionality, but only to keep a session going to the same pool, and not s...
Jason_Hook_4092Nimbostratus
NimbostratusYeah,
if not /streamer client A then pool A else pool B (then set a session cookie to route faster for subsiquent requests)
if /streamer and client A, then pool A2 + PERSIST else pool B2 + PERSIST
I'm shooting for 4 pools, A1/A2 and B1/B2...the 1's would be Observed method (best that I found for regular web requests) and the 2's would be least connections since all of the /streamer connections are long running and I just want to balance based on connection count and not performance like Observed offers.
make sense? sound like a clean solution?