DEV Community

Cover image for Alfresco Search Services Optimization: SOLR Indexing, Query Performance & Reindexing
shikha
shikha

Posted on Originally published at shikhanirankari.blogspot.com

Alfresco Search Services Optimization: SOLR Indexing, Query Performance & Reindexing

As an Alfresco repository grows, search problems can become increasingly visible:

Newly uploaded documents take too long to appear in search
Full-text searches become slower
SOLR falls behind repository transactions
Reindexing takes hours or even days
JVM, disk or database utilization increases
Queries that worked well on smaller repositories become expensive

But optimizing Alfresco Search Services isn't simply about giving SOLR more memory.

Search performance is influenced by the complete processing chain:

Repository → Database → SOLR Trackers → Transformation → Index → Query → ACL Filtering

In my latest technical guide, I explore:

🔹 How Alfresco SOLR indexing works
🔹 Metadata, ACL and Content Tracking
🔹 Understanding Indexing Lag
🔹 Full-Text indexing and transformations
🔹 Query performance optimization
🔹 Wildcard and field-specific queries
🔹 JVM and filesystem-cache considerations
🔹 Disk I/O and storage performance
🔹 ACL impact on searches
🔹 Sharding for large repositories
🔹 When a full reindex is actually required
🔹 Reindexing large production repositories
🔹 Database and transformation impact during reindexing
🔹 Post-reindex validation
🔹 Production monitoring and troubleshooting

One important lesson

A search problem doesn't automatically mean:

“Delete the SOLR index and reindex everything.”

For large enterprise repositories, a full reindex can be an expensive operation.

Before rebuilding an index, investigate:

Indexing Lag → Trackers → Transformations → Custom Models → Permissions → JVM → Storage → Database → Network

Only then should reindexing become part of the recovery strategy.

Large Repository Reindexing

For large repositories, simply deleting the production index and rebuilding it can result in significant search downtime.

Where the supported architecture and available infrastructure permit it, a safer strategy can be:

Existing Search remains available → Build new index → Track/Reindex → Validate → Cut over

The objective isn't just to rebuild SOLR.

It's to rebuild it predictably, validate it properly and protect production search availability.

📖 Complete English guide:

https://shikhanirankari.blogspot.com/2026/08/alfresco-search-services-solr-optimization.html

🇫🇷 Version française:

https://shikhanirankari.blogspot.com/2026/08/optimisation-alfresco-search-services-solr.html

What has been the most challenging part of Alfresco Search in your environment — indexing lag, query performance, ACLs, reindexing or infrastructure sizing?

Top comments (0)