jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2407) Make the disk space used by cached binary properties configurable
Date Wed, 25 Nov 2009 09:10:39 GMT

    [ https://issues.apache.org/jira/browse/JCR-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782345#action_12782345
] 

Stefan Guggisberg commented on JCR-2407:
----------------------------------------

deletion of the temp files is triggered by gc. rather than limiting the disk space we should
investigate why the temp files aren't collected.
maybe there are places where the reference is not cleared. 

i assume the problem only occurs in in certain configurations where the binary values are
stored in a db (pm or data store).

it might also be related to the size of the temp files (smaller binary values should be kept
entirely in memory).

> Make the disk space used by cached binary properties configurable
> -----------------------------------------------------------------
>
>                 Key: JCR-2407
>                 URL: https://issues.apache.org/jira/browse/JCR-2407
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.0-beta1
>            Reporter: Martijn Hendriks
>
> Binary properties which are in Jackrabbit's caches (SharedItemStateManager eg) are stored
on disk in the temp dir. This can cause problems on small temporary file systems as the size
of the binary properties on disk is not limited by Jackrabbit. There is one way to influence
this indirectly: make the Jackrabbit cache sizes smaller (via the CacheManager). It could
be helpful in some cases if an upper bound on the disk usage can be given. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message