Forum Discussion
Rikardo_77456
May 10, 2011Nimbostratus
Hi Aaron, thanks for the reply.
No, both members are available the whole time. Could it be something to do with persistence of another pool crossing over? It's the only explanation I can think of.
How we have it set up is one virtual server that by default sends http traffic through pool1 (this includes 2 members, that have cookie persistence), but have an irule that checks the uri for a specific starting string. If the uri starts with this specific string we send it to pool2 (problem pool, as stated above. This includes the same members as pool1, but instead of load balancing we are trying to use priority groups in an active/passive type setup, so that traffic only ever gets sent to one member at a time). Could it be that because the user has already been through pool1, and has a cookie to persist this, that when they get passed through pool2 they get sent to the same member as in pool1? I don't fully understand the cookie persistence and if this could be the case?
Rikardo