---
title: Managing the global indexes in entry-balancing configurations
description: Overview of the PingDirectoryProxy global indexes that route operations to the correct backend set, including creating, reloading, sizing, and priming them.
component: pingdirectory
version: 11.1
page_id: pingdirectory:pingdirectoryproxy_server_administration_guide:pd_proxy_manage_global_indexes_entry_bal_configs
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectoryproxy_server_administration_guide/pd_proxy_manage_global_indexes_entry_bal_configs.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: September 13, 2023
---

# Managing the global indexes in entry-balancing configurations

In an entry-balancing configuration, the PingDirectoryProxy server maintains the default relative distinguished name (RDN) index as well as one or more in-memory global attribute indexes.

The global indexes allow the PingDirectoryProxy server to select the correct backend server set for incoming operations, which avoids broadcasting operations to all backend sets.

The indexes can be preloaded from peer proxies or the backend directory servers when the server starts up and are updated by certain operations that come through the PingDirectoryProxy server. For example, when a new entry is added, the distinguished name (DN) of the new entry is added to the DN index of the PingDirectoryProxy server performing the operation. The indexes are also fault-tolerant and can adapt to changes made in the backend servers without going through the PingDirectoryProxy server. For example, operations are processed directly through the backend server.

This section describes:

* When to create a global attribute index

* How to reload the global index

* How to monitor the global index growth

* How to prime the global index from a peer at startup