Is there a way to rebuild our CQ's (5.6) search index without incurring downtime and having to stop the instance?

Hi Sham,

Would this work without restart: http://docs.adobe.com/docs/en/cq/current/deploying/upgrading/consistency-check.html?

If so, do we have to do it on each instance separately?

Thanks.

LinearGradient wrote...

Hi Sham,

Would this work without restart: http://docs.adobe.com/docs/en/cq/current/deploying/upgrading/consistency-check.html?

If so, do we have to do it on each instance separately?

Thanks.

 

You can run  without restart during non peak load time

Yes, it is possible to rebuild the search index in CQ5 (5.6) without incurring downtime or restarting the instance. Here's how you can do it:

Rebuilding Search Index in CQ5 without Downtime:

1. Use the Index Rebuilder Tool: AEM provides an index rebuild tool (/bin/reindex) to rebuild the search index without needing to restart the instance. You can access this tool by navigating to: http://<host>:<port>/bin/reindex

2. Trigger Reindexing:

   • This will initiate the reindexing process for the repository. It may take time depending on the size of the data and the number of nodes in the repository.

3. Rebuild Specific Index: If you're facing issues with specific search indexes, you can rebuild only the index that corresponds to your issue. In CQ5, there are different types of indexes (e.g., Lucene, Oak indexes). To rebuild a particular index, you may need to run: curl -u <username>:<password> -X POST http://<host>:<port>/bin/reindex/<index-name>
   
   

   Running Consistency Check without Restart:

   1. JCR Consistency Check: To ensure the repository is consistent and free from corruption, you can run the consistency checker. In AEM, this can be done via the JCR console, typically under /libs/crx/system/console/jcr/repository-consistency.

   2. Run the Check:

      • Go to the Repository Consistency section of the CRX repository.
      • Click the Check button to perform the consistency check. This operation checks if the repository's integrity is intact, and it does not require restarting the instance.

   Important Notes:

   • The index rebuilding might slow down the system momentarily, but it won't take the system down.
   • For production environments, always ensure you have backups before triggering large operations like reindexing.

   By using these methods, you can fix indexing and consistency issues without any downtime.