[ https://issues.apache.org/jira/browse/DIRSERVER-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny updated DIRSERVER-1747: ----------------------------------------- Description: When we start the server the very first time, the initialization tries to load the entries which have an administrative-role AT. It uses the (administrative-role=*) filter, which uses the Presence index. The evaluation done in the backend considers that we have an Long.MAX_INTEGER candidate. That will result in a full scan, which is extremely costly when we have a lot of entries. We should add an index for the administrative-role, and for some other AT that are loaded in cache at startup. was: When we start the server the very first time, the initialization tries to load the entries which have an administrative-role AT. It uses the (administrative-role=*) filter, which uses the Presence index. The evaluation done in the backend considers that we have an Long.MAX_INTEGER candidate, which is obvioulsy wrong. That will result in a full scan, which is extremely costly when we have a lot of entries. Priority: Major (was: Critical) Issue Type: Improvement (was: Bug) > Presence index is not up to date when the server is started > ----------------------------------------------------------- > > Key: DIRSERVER-1747 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1747 > Project: Directory ApacheDS > Issue Type: Improvement > Affects Versions: 2.0.0-M7 > Reporter: Emmanuel Lecharny > Fix For: 2.0.0-M8 > > > When we start the server the very first time, the initialization tries to load the entries which have an administrative-role AT. It uses the (administrative-role=*) filter, which uses the Presence index. The evaluation done in the backend considers that we have an Long.MAX_INTEGER candidate. > That will result in a full scan, which is extremely costly when we have a lot of entries. > We should add an index for the administrative-role, and for some other AT that are loaded in cache at startup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira