Pool persistence almost lost after a pool member has been marked down

Hi,

Without clarification how you figure out that requests destined (based on cookie) to N3 are going to N2 it's hard to say what's going on.

Anyway - forgot about changing Action on Service down changes for HTTP traffic - if you wish to faster inform clients that member is down you can set it to Reject (if I can recall) but for sure Reselect will not work.

Possible reason for request with cookie pointing to N2 being directed to N3 is lack of OneConnect. Without it LB is done on per TCP connection basis. Once TCP connection is directed to given member all packets belonging to this connection will be send to this member.

If inside this TCP connection client will send HTTP request with cookie pointing to N3 (assuming that connection was LB o N2) this request will land on N2.

So it's necessary to do the trace and review what headers are in client HTTP request (inside one TCP connection).

Piotr