Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Queries regarding Lucene indexing.

Avatar

Level 2

Hi,
When I am trying to modify my search indexing configurations on my 5.4 instance, as mentioned in the following links: https://helpx.adobe.com/experience-manager/kb/SearchIndexingConfig.html and http://wiki.apache.org/jackrabbit/IndexingConfiguration.\ 
I found two index folders under the following locations. 
<crx-quickstart>\repository\repository\index.
<crx-quickstart>\repository\worskpaces\crx.default\index. I wanted to know where the actual indexing happens. 

Thank you.

1 Accepted Solution

Avatar

Correct answer by
Level 10

The CRX repository of CQ 5.4 has multiple workspaces for versioned nodes and regular content nodes. And for each workspace you will see Lucene indexes created in different locations. Check the below link[1] to see the list of indexes and which is what. 

[1] http://www.wemblog.com/2011/09/which-index-is-what-in-cqcrx.html 

View solution in original post

3 Replies

Avatar

Correct answer by
Level 10

The CRX repository of CQ 5.4 has multiple workspaces for versioned nodes and regular content nodes. And for each workspace you will see Lucene indexes created in different locations. Check the below link[1] to see the list of indexes and which is what. 

[1] http://www.wemblog.com/2011/09/which-index-is-what-in-cqcrx.html 

Avatar

Level 2

Thanks Kunal. 

Let us say,we have a scenario where I have a huge content. Which would be the ideal way to index this huge content, in order to have a lesser downtime ?

Avatar

Level 10

In CQ 5.x you can rebuild indexes but for that you will have to shut down the instance and restart it. And for big repositories the rebuilding time can be many hours and sometimes it may go beyond a day. In such a scenario, you should optimize your indexing configuration in such a way to index only the content/nodes which are relevant and configure indexing features which are needed. For example if you don't use auditing reports then you can remove those indexes. See link [1]. Also, to reindex big repository there is an option to rebuild the indexes (offline with the backup) so that the downtime can be minimized. See link [2]. 

 

[1]  https://helpx.adobe.com/experience-manager/kb/how-to-optimize-lucene-index-to-gain-efficiency.htm
      https://docs.adobe.com/docs/en/cq/5-6-1/deploying/performance.html#Search Indexing

[2] http://www.wemblog.com/2011/09/how-to-reindex-large-repository.html