AEM Vanity URL take too long to update

Avatar

Avatar

Manh_Nguyen

Avatar

Manh_Nguyen

Manh_Nguyen

15-04-2019

Hi,

When we add a new or update a vanity URLs to the page and save the config. The changes are not reflected immediately. But after few hours later, we do a check again, then the vanity URL can be used.

I also did a check right after creating a new vanity URL for my page, on Sling Resource Resolver (/system/console/jcrresolver), but nothing was updated as I can observe. But after few hours, the new vanity URL has been appeared on Sling Resource Resolver mapping, and I can use this Vanity URL.

From what I understand, vanity URL should be reflected immediately after I created or updated the vanity URL. But now it's taking too long.

Is there anything wrong for my system? Any help would be greatly appreciated.

My version is AEM 6.2 Sp1 CFP-14.

Thanks,

Manh

View Entire Topic

Avatar

Avatar

Kunwar

Employee

Avatar

Kunwar

Employee

Kunwar
Employee

18-04-2019

I think the vanitybloom filter is either bloated or the query that refreshes the vanity filter is slow on your instance.

A quick try would be run query [1] after yo update or add a new vanity path and see if you can fetch the node in the query resultset

Read more about VanityBloomFilter at Apache Sling :: Mappings for Resource Resolution

[1] : SELECT sling:vanityPath, sling:redirect, sling:redirectStatus FROM sling:VanityPath WHERE sling:vanityPath IS NOT NULL