[
https://issues.apache.org/jira/browse/DIRSERVER-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255111#comment-13255111
]
Carlo Accorsi commented on DIRSERVER-1711:
------------------------------------------
Hi, After this fix, i created an entirely new server. After Creating indexes
and restarting, i imported 80 users. The server has the same issue once i
restart.
jvm 1 | calling WrapperListener.start()
jvm 1 | Waiting for WrapperListener.start runner thread to complete.
jvm 1 | WrapperListener.start runner thread started.
wrapper | Startup failed: Timed out waiting for signal from JVM.
wrapper | JVM did not exit on request, terminated
wrapperp | server listening on port 32000.
wrapper | JVM was only running for 30 seconds leading to a failed restart
count of 1.
wrapper | There were 1 failed launches in a row, each lasting less than 300
seconds. Giving up.
wrapper | There may be a configuration problem: please check the logs.
wrapper | <-- Wrapper Stopped
> Index initialization is taking way too much time
> ------------------------------------------------
>
> Key: DIRSERVER-1711
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1711
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 2.0.0-M6
> Reporter: Emmanuel Lecharny
> Fix For: 2.0.0-M7
>
>
> When we add some new ATs to be indexed, they are created at startup. As the
> buildUserIndex() method is called for every single index, and as the master
> table is being browsed during this process, indexing 10 AT will result into
> the master table to be read 10 times, which is extremely costly....
> We must process all the index in one shot, reading the Master table only once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
