Forum Discussion
Receive Disable string functionality with persistence enabled
I too had this concern, I tried going with forced-offline too. But was also reported that persistent connections were still present. Hence had to manually clear out the persistent entries, that's what the article says too.
Also, I stumbled upon this
feature, where I had set this to reject state. It did made some difference. Since I was unable to generate much load test, I can't confirm if this is going to satisfy your need, may be you test this out.action on service down
Put your member to forced-offline with action on service to reject and update us.
Also I had happened to save this once, haven't tested though.
when SERVER_CONNECTED {
TCP::collect
}
when SERVER_DATA {
if { [active_members -list [LB::server pool]] contains [LB::server addr] } then {
TCP::release
} else {
Use TCP::close to close the connection after the next response
TCP::close
User reject to terminate the request immediately
reject
}
}
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com