Over time, stale entries can build up in the global indexes because proxies do not communicate changes to the indexes with one another. The Directory Proxy Server continues to operate normally in this situation since the global indexes are only ever used as a hint at where to find entries.
The rate of this growth is typically very slow since in most environments the key attributes change infrequently. The global indexes themselves are also very compact. However, if the global indexes start to fill up the allocated memory, you may need to flush and reload them. The size of the global indexes can be monitored over LDAP using the following command:
$ bin/ldapsearch -b "cn=monitor" -D "uid=admin,dc=example,dc=com" -w password \ "(objectClass=ds-entry-balancing-request-processor-monitor-entry)" \ global-index-current-memory-percent
If the global indexes fill up, the Directory Proxy Server will continue to operate normally, but it will need to start evicting entries from the indexes, which will lead to more broadcast searches, reducing the overall throughput of the Directory Proxy Server.
To reload the indexes so that they no longer hold stale information, run the reload-index command with the --fromDS option so that data is loaded from backend directory servers. We recommend that you reload the indexes during off-peak hours because it may have an impact on performance while the reload is in progress.