[
https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248824#comment-14248824
]
Vikas Saurabh commented on SLING-4216:
--------------------------------------
[~asanso], I tried reading through the patch (unfortunately, I couldn't apply
it on the trunk of my local repo :-/ ... I'm sure that's ignorance on my part
though :)). Anyway, afaics, size of bloom filter can only be set once and then
from next time on it'd respect the size according to persisted file length. I
think if we want to expose filter size as properties, we'd need to clear up old
persisted data when the properties are updated (or probably when a mismatch is
detected between property value and file's size). Again, I'm sorry if I might
have missed it and it's already being taken care of -- browser wasn't the best
tool to read through the patch :(
> Limit the number of vanityPath MapEntry
> ----------------------------------------
>
> Key: SLING-4216
> URL: https://issues.apache.org/jira/browse/SLING-4216
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
> Attachments: SLING-4216-patch.txt, SLING-4216-patch.txt,
> SLING-4216-patch.txt
>
>
> At the moment there isn't any limit to the number of MapEntry that are cached
> in memory.
> If the number of vanityPaths/alias is extremely high this can cause OOM.
> It would be good to have a way to limit the amount of memory used by the
> MapEntry cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
