svn commit: r1653002 - /sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext

[as...@apache.org]

Author: asanso
Date: Mon Jan 19 13:57:59 2015
New Revision: 1653002

URL: http://svn.apache.org/r1653002
Log:
SLING-4216 - Limit the number of vanityPath MapEntry

* document how to rebuild the bloom filter

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext?rev=1653002&r1=1653001&r2=1653002&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext Mon Jan 19 13:57:59 2015
@@ -166,3 +166,15 @@ The following pseudo code shows this alg
         }
     }
 
+## Rebuild The Vanity Bloom Filter 
+
+<a href="https://issues.apache.org/jira/browse/SLING-4216">SLING-4216</a> introduced the usage of a bloom filter in order to resolve long startup time with many vanityPath entries.
+The bloom filter is handled automatically by the Sling framework. In some cases though, as changing the maximum number of vanity bloom filter bytes, a rebuild of the vanity bloom filter is needed.
+
+In order to rebuild vanity bloom filter:
+
+* stop Apache Sling
+* locate the org.apache.sling.resourceresolver bundle in the file system (e.g. $SLING_HOME/felix/bundleXX)
+* locate the vanityBloomFilter.txt file in the file system (e.g. $SLING_HOME/felix/bundleXX/data/vanityBloomFilter.txt)
+* delete the vanityBloomFilter.txt file
+* start Apache Sling (this might take few minutes, depending on how many vanity path entries are present)