The proxies don't communicate changes to the indexes with one another, which can result in stale entries building up over time in the global indexes. In this situation, the PingDirectoryProxy server continues to operate normally because the global indexes are used only as a hint for where to find entries.

The rate of this growth is typically slow because in most environments the key attributes change infrequently. In addition, the global indexes are compact. However, if the global indexes start to fill up the allocated memory, you might need to flush and reload them.

If the global indexes become full, the PingDirectoryProxy server continues to operate normally, but it needs to start evicting entries from the indexes. Evicting the entries leads to more broadcast searches and reduces the overall performance of the PingDirectoryProxy server.

  • To monitor the size of the global indexes over LDAP, use the ldapsearch with the global-index-current-memory-percent option.
    $ bin/ldapsearch -b "cn=monitor" -D "uid=admin,dc=example,dc=com" -w password \
      "(objectClass=ds-entry-balancing-request-processor-monitor-entry)" \
  • To reload the indexes so they no longer hold stale information, run the reload-index command with the --fromDS option.

    This option ensures that data is loaded from backend directory servers.


    You should reload the indexes during off-peak hours because it might impact the performance while the reload is in progress.