switch matching incorrectly

Thanks for clarifying this.

Can you determine which wrong pool it is going to 20% of the time?

Is it the gwp_pool or is it some other arbitrary pool?

Here are some other steps that might be useful in getting more to the bottom of this:

It might be useful to add a log statement in the /gwp* portion of the switch, just to make sure that it isn't somehow inadvertently matching.

To determine the pool, you could add an LB_SELECTED event add log the selected pool, like so:

 
 when LB_SELECTED { 
    log "picked: [IP::remote_addr] from pool: [LB::server pool]" 
 } 
 

There are also other LB::server commands that can be used after the load-balancing decision has been made. So, in events like: LB_SELECTED, LB_FAILED, & SERVER_CONNECTED you can use the LB::server command to determine some of the aspects of the load balancing decision. Here are the forms of the command:

[LB::server] - returns a Tcl list with pool, node addr and port.

[LB::server name] - same as above

[LB::server pool] - returns the pool name.

[LB::server addr] - returns the selected pool member's address.

[LB::server port] - returns the selected pool member's service/port.

[LB::server priority] - returns the selected pool mbr's priority.

[LB::server ratio] - returns the selected pool mbr's current ratio.