Forum Discussion
Please explain me the use of "Reselect on Service Down" and "Least Connection" and also which is better? Consider me new to this
When a pool member fails to respond to a health monitor, the system marks that pool member down and removes any persistence entries associated with the pool member. The BIG-IP system continues to monitor the pool member to determine when the member becomes available again. While a pool member is marked down, the system does not send any new connections to that pool member.
The Action On Service Down feature specifies how the system should respond to already-established connections when the target pool member becomes unavailable.
None
The BIG-IP system takes no action on existing connections, and removes the connection table entry based on the associated profile's idle timeout value. The BIG-IP system sends a TCP Reset (RST) or ICMP Unreachable once idle timeout is reached. This is the default setting. This is the best option for most common scenarios, as this allows for endpoints to resume gracefully on their own. This may be a good choice for clients that transfer large amounts of data, as the pool member may recover itself before the connection is reset, allowing the large transfer to continue.
Reject
The BIG-IP system sends RST or ICMP messages to reset active connections and removes them from the BIG-IP connection table.This may be a good choice for clients that need to be notified of pool member state changes sooner than the configured idle timeout period for that virtual server. Once the target pool member is deemed unavailable, the BIG-IP system immediately alerts the client by resetting the connection, causing the client to attempt a new connection.
Drop
The BIG-IP system silently removes the connection table entry. You should carefully consider this option, as the client receives no feedback from the BIG-IP system regarding the connection state. However, this option works well for short-lived, connectionless protocols, such as UDP. For example, DNS queries.
Reselect
The BIG-IP system manages established client connections by moving them to an alternate pool member without a connection teardown or setup.
---------- Least Connection
Least connection is all together a different thing. Its a pure load balancing algorithm. It measure the current connection on every pool member based on the number on entries in its connection table. The lower is always treated best. If in case any pool member goes down, it will simply tear its existing connections and use remaining pool members (starting from the one with least number of connections).
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