Manual Chapter :
Solve a performance issue due to pool member status
Applies To:
Show Versions
BIG-IQ Centralized Management
- 8.3.0, 8.2.0, 8.1.0, 8.0.0
Solve a performance issue due to pool member status
Before you start, you probably want to create a replacement pool member to handle the traffic of the problem member.
When you isolate a pool member that is affecting traffic performance, you have a couple of ways to remedy the issue. Depending on what kind of issues the pool member is experiencing, you might want to delete it immediately, disable it, or force it offline.
- Select the application that needs attention from the all applications screen ().
- Find the pool member that needs attention: At the right, center of the screen, click the number in the Servers circle.This displays the pool member information in the CONFIGURATION area.
- Select the pool member that needs attention:
- ClickCONFIGURATION.
- Select the check box for the pool member.
- Determine what you want to do with this pool member based on the nature of the performance issue, and take the most appropriate action.What do you want the member to do?Select this optionCease all traffic immediatelySelectDelete.BIG-IQ removes the pool member from the pool, but does not delete the associated node.This option is most appropriate when an issue requires a quick response. Current connections will be interrupted.Stop processing new connections but continue to process persistent or active connections.SelectDisable.BIG-IQ continues to process persistent and active connections for this member. New connections are accepted only if they belong to an existing persistence session.This option is appropriate when you can afford the time for traffic to dissipate before the member stops processing traffic.Stop processing new connections but continue to process active connections.SelectForce Offline.BIG-IQ continues to process active connections for this member. New connections are accepted only if they belong to an existing persistence session.This option is appropriate when you can afford the time for traffic to dissipate before the member stops processing traffic.
The next thing you probably want to do is repeat the troubleshooting steps you used to isolate this pool member as the problem source and confirm that the issue is resolved.
