Table of Contents
Advertisement
Managing Indexes
Symptoms of an Inappropriate All IDs Threshold
Value
When your All IDs Threshold is set incorrectly, you will see poor search
performance. However, poor search performance can be caused by other factors.
For example:
•
Your users are performing a lot of searches for which you are not maintaining
an index.
•
Your database cache size and entry cache size may be set incorrectly. See
Chapter 14, "Tuning Directory Server Performance" for more information.
Carefully examine these possibilities first before changing your All IDs Threshold
value.
If you think that your server is suffering from an All IDs Threshold that is too low,
look in your access log. See Chapter 12, "Monitoring Server and Database
Activity." Any searches that resulted in all entry IDs being returned will contain
the
notes=U
•
Searches for which you are not maintaining an index
•
Searches for which an ID list is not maintained because the All IDs Threshold
value has been reached for that index key
To determine whether the search result belongs to a search that should have been
indexed, you have to match the
previous SRCH line in your access log file. The SRCH line will show the search
filter that was used for the search request. If you have an index for the specified
search filter, then the notes=U flag results from the All IDs Threshold value being
reached for the index key. For example, the access log looks as follows:
[24/July/1998:15:12:20 -0800] conn=2 op=1 SRCH base="o=example.com"
scope=0 filter="(cn=James)"
[24/July/1998:15:12:20 -0800] conn=2 op=1 RESULT err=0 tag=101
nentries=10000 notes=U
The presence of the
reached for the
378
Netscape Directory Server Administrator's Guide • August 2002
flag. The
flag will be returned for:
notes=U
conn
flag indicates that the All IDs Threshold has been
notes=U
attribute index.
cn
and
values from the RESULT line to a
op
Advertisement
Table of Contents
Troubleshooting
