topic Re: Cascade Tracker becomes very slow in Alfresco Forum

Cascade Tracker becomes very slow

nschwalbe — Fri, 13 Sep 2019 10:11:51 GMT

We are upgrading our Alfresco 5.2 community edition with Solr 4 index to Alfresco 6.1 with Solr 6.Everything went fine until we tried the upgrade with our production data. The solr6 index is successfully build within 1-2 hours and searching is possible but the Cascade Tracker which updates the path

Re: Cascade Tracker becomes very slow

afaust — Fri, 13 Sep 2019 11:25:15 GMT

On what kind of infrastructure are you running this Docker-based deployment? Given the extremely long times to load metadata / update the index, I am left wondering if there are any excessive IO / network delays. I am also not quite clear on why the cascade tracker is running at all - if you have just built the SOLR 6 index from scratch, I would not expect there to be any transactions to cascade, unless those have been created since the build was completed.

Did you happen to perform a memory dump of the SOLR process to see which parts of the application caused the high memory issue? It is often hard to guess remotely what may be going on (especially in a scenario that appears to be quite strange to me), without having actual memory measurements / analysis results.

Re: Cascade Tracker becomes very slow

nschwalbe — Fri, 13 Sep 2019 12:15:22 GMT

Hi Axel,

thanks for your quick answer. We are currently testing it on one docker host which is on a vmware VM with a SAN storage. By writing this, I remember that I read something about bottlenecks on SAN storage. Maybe we try it with a local storage.

The cascade tracker becomes that slow after initial indexing finishes. We have not created or modified any documents in between.

I have no memory dump but I will do one ...

Re: Cascade Tracker becomes very slow

nschwalbe — Thu, 19 Sep 2019 11:22:46 GMT

Finally after some debugging I found the problem. There are cmerson nodes with >20,000 paths. This happens because we have many sites and the user has paths in any site. FortunateIy I found a toggle in the source code to ignore these nodes. After some searching for that toggle I found out that I need to set the following properties.

On ACS:

search.solrTrackingSupport.ignorePathsForSpecificTypes=true

On Solr 6 in solrcore.properties or shared.properties

alfresco.metadata.skipDescendantDocsForSpecificTypes=true
alfresco.metadata.ignore.datatype.0=cm:person
alfresco.metadata.ignore.datatype.1=app:configurations
alfresco.metadata.ignore.datatype.2=cm:authorityContainer