[
https://issues.apache.org/jira/browse/DIRSERVER-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1534.
------------------------------------------
Resolution: Invalid
This is an old issue, I'm not sure it's really accurate anymore.
There are two places were we can laod entries from LDIF files when starting the
server :
- when we use @ApplyLdifFiles annotation
- when we have some test entries to load into the server at startup.
The first use case is not a problem : we process the entries one by one, they
never stay in memory.
The second use case is probably not a problem : it's quite rare that we have to
load a multiple-gigabytes file at startup to do tests.
I close this issue as 'invalid', but feel free to reopen if there is a more
critical need.
> Improving implementation of loading LDIF files during startup
> -------------------------------------------------------------
>
> Key: DIRSERVER-1534
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1534
> Project: Directory ApacheDS
> Issue Type: Improvement
> Reporter: Kiran Ayyagari
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> Currently the way we load LDIF file data during startup might lead to OOM,
> cause we prase the LDIF file and keep all the LdifEntry objects in memory.
> This has to be handled in a better way by avoiding storing of all the
> LdifEntry objects in memory.
--
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
