[
https://issues.apache.org/jira/browse/JCR-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-1999.
-----------------------------------
Resolution: Duplicate
I'll resolve this as a duplicate of JCR-1818. The cause of this issue is
basically the same. Smaller index segments wait to be merged while larger index
segments are being merged.
> Index curruption after XML import
> ---------------------------------
>
> Key: JCR-1999
> URL: https://issues.apache.org/jira/browse/JCR-1999
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: core 1.4.5
> Reporter: Marcel Reutegger
> Priority: Minor
> Attachments: repository_import_nudge.zip, repository_webapp.log.zip
>
>
> This was reported on the user list.
> After an XML import the repository is immediately shutdown, which seems to
> leave the index in a corrupted state. I suspect this is because the index
> merger is terminated, as can be seen from the log:
> ...*repository initialized*
> ...*basic read: find a node, read it's name*
> ...*repository is shutting down*
> 5198 [main] INFO
> org.apache.jackrabbit.core.observation.ObservationDispatcher - Notification
> of EventListeners stopped.
> 5698 [main] INFO org.apache.jackrabbit.core.query.lucene.IndexMerger - *Unable
> to stop IndexMerger. Deamon is busy.*
> 6009 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index
> closed: /var/jackrabbit/repository/workspaces/default/index
> 6022 [main] INFO
> org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager -
> Database '/var/jackrabbit/repository/workspaces/default/db' shutdown.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
