---
title: Removing the engine from the load balancer configuration
description: Remove the engine from the load balancer configuration. Because this step is dependent on your environment, no specific instruction will be provided.
component: pingaccess
version: 9.1
page_id: pingaccess:pingaccess_zero_downtime_upgrade:pa_removing_the_engine_from_the_load_balancer_configuration
canonical_url: https://docs.pingidentity.com/pingaccess/9.1/pingaccess_zero_downtime_upgrade/pa_removing_the_engine_from_the_load_balancer_configuration.html
llms_txt: https://docs.pingidentity.com/pingaccess/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: May 8, 2024
section_ids:
  before-you-begin: Before you begin
  steps: Steps
---

# Removing the engine from the load balancer configuration

Remove the engine from the load balancer configuration. Because this step is dependent on your environment, no specific instruction will be provided.

## Before you begin

You must be familiar with the steps required to temporarily remove the engine from your load balancer configuration.

|   |                                                                                                                                                                                                                                                                                                                                                                            |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | To maintain resource availability, you should remove only the engine you are upgrading. After the upgrade is complete, add the engine back to the load balancer configuration. Only after you confirm that the engine has been successfully added to the load balancer and is reporting properly to PingAccess should you begin the upgrade process on additional engines. |

The following flowchart demonstrates engine removal.

![Flowchart showing a deployment as an engine is removed from the load balancer.](_images/qht1564006856570.png)

In the previous flowchart:

1. A user with a WebSession Cookie sends a request to the load balancer.

2. The load balancer directs the request to one of the other two engine nodes. All of the engine nodes are still using the source version of PingAccess.

3. The administrative node is using the target version of PingAccess.

## Steps

1. Identify and note the engine you want to upgrade. Ensure you have the engine definition for this engine available.

2. Remove the engine from the load balancer.

   |   |                                                                                                                                                                                                             |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | Keep a record of the changes you make so that you can reverse this operation later in [Adding the engine to the load balancer configuration](pa_adding_the_engine_to_the_load_balancer_configuration.html). |

3. Restart the load balancer.