[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244094#comment-14244094 ]
Vikas Saurabh commented on SLING-4216: -------------------------------------- bq. And I did actually did not change my mind :) bq. At the end of the day IMHO if a situation like you said will happen (possible but unlikely) it is better to rebuild the bloomFilter file from scratch I agree although even finding that such a change has happened is equally expensive (from repo read point of view) > 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 > > > 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)