Single Node Persistence
Problem this snippet solves: A really slick & reliable way to stick to one and only one server in a pool.
Requirement: Direct traffic to only a single node in a pool at a time. Initially, traffic ...
Published Mar 18, 2015
Version 1.0
StephanManthey
Nacreous
NacreousHi Dominique, I would recommend to create a new dest address affinity persistence profile with an appropriate timeout. It will be used as default persistence profile and replaces the iRule logic. Please use action on service down in the advanced pool config with the parameter of "reject" to terminate current connections in a case of pool members state change. With a state change the persistence record will be deleted and a new incoming connection will be balanced to another available pool member. A new persistence record will be created. Please keep in mind, that the record will be updated by new incoming connections only. That's why you will notice a reset of the remaining time only with newly established connections. Cheers, Stephan