You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/09/23 16:40:26 UTC

[jira] [Resolved] (JCR-2492) Garbage Collector remove data for active node

     [ https://issues.apache.org/jira/browse/JCR-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-2492.
--------------------------------

    Resolution: Duplicate

> Garbage Collector remove data for active node
> ---------------------------------------------
>
>                 Key: JCR-2492
>                 URL: https://issues.apache.org/jira/browse/JCR-2492
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 1.4
>         Environment: Linux 2.6.x (gentoo or fedora), JDK 1.5 (sun or jrockit), JBoss 4.2.3.GA, Derby (10.4.1.3), PostgreSQL (8.1.11 or 8.0.3)
> * FileSystem = LocalFileSystem
> * custom AccessManager
> * PersistenceManager = PostgreSQLPersistenceManager
> * SearchIndex, textFilterClasses = ""
> * DataStore = FileDataStore (minLogRecord = 100)
>            Reporter: Cédric Chantepie
>            Priority: Critical
>              Labels: collector, data, datastore, garbage, lost
>
> When we use GarbageCollector on a 42Gb datastore, GarbageCollector erase all data.
> Back with node, none have any longer data : jcr:data was removed as data in datastore no longer exist.
> On some smaller test repository, this trouble does not occur.
> We will try to update Jackrabbit version, but at least it could be "good" to be sure what is really the trouble with GC in Jackrabbit 1.4.5 so that we can be sure that updating it will really fix that.
> Thanks.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira