Loading...
Loading...
In rare circumstances while using least-connections load balancing with a connection limit applied, if a pool member is at the connection limit and the node is stopped and restarted, the node will remain marked down.
Pool member remains marked down.
This occurs under the following circumstances: - Least Connections (node or member). - Connection limit is set. - Then a pool member hits the connection limit. - The pool member is then marked down then up (e.g., manually).
This condition is very rare but if it occurs you can try removing the pool member or node and re-adding it.
Connection limit is now correctly enforced with least-connections and pool member flap, so the member no longer incorrectly remains down.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.