Forum Discussion
karthic_n_12765
Nimbostratus
Mar 02, 2004enable/disable vs up/down
1. Does calling Node::set_state() with "disabled" prevent new connections from being directed to the node unless they belong to a persistence session already established on that node?
2...
Mar 03, 2004
the set_availablity() method should be used to "bleed" connections from a node. This means that no NEW connections will be processed to that server. This equates to the "Enable/Disable Sessions" option in the GUI. From the GUI docs:
If sessions are disabled, no new sessions can be sent to the node. Clients with persistent connections remain connected to the node and can start new sessions until they timeout based on the persistens setting for the pool the node is a member of.
The set_state() method is used to sever all connections to a back end server. Again, from the GUI docs.
If connections are disabled, no traffic can be sent to the node. This is a Forced Down state. To take the node down without interrupting current client sessions, set the availablility to disabled. Once all traffic has timed out from the node, disable connections to stop all further traffic to the node
As for determining the traffic a node is receiving, you should use the current connections in the connection statistics and monitor this until the count reaches zero after you have set the availablitity to disabled.
-Joe
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects
