Expand my Community achievements bar.

SOLVED

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

Avatar

Level 7

Hi,

Looks like we have some nodes in CRXDE that do not show in search results. Is there a way to fix this issue without restarting our instance (actually we have a 2-instance cluster).

Also, is there a way to run a consistency check without restarting CQ5?

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Level 10

Restart is required , however you can minimize the time by following http://www.wemblog.com/2011/09/how-to-reindex-large-repository.html

View solution in original post

4 Replies

Avatar

Correct answer by
Level 10

Restart is required , however you can minimize the time by following http://www.wemblog.com/2011/09/how-to-reindex-large-repository.html

Avatar

Level 7

Hi Sham,

Would this work without restarthttp://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.

Avatar

Level 10

LinearGradient wrote...

Hi Sham,

Would this work without restarthttp://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

Avatar

Level 3

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.