reindexing

[#1]

I have done the purge activity and trying to re-index.

As a part of re-indexing i have deleted the folder index under /crx-quickstart/repository.

After the start of the instance i see the re-index doesnt happen and when i trigger from crxde by setting the reindex to true then reindex happened .

Ideally re-index should happen when the index folder is deleted and restarted the instance and what should be wrong in this scenario?

[#2 · Accepted solution]

Be aware, that "reindexing" is something which was done way to often in the past, and in most cases it was not necessary at all and sometimes even caused more issues. Please performa a reindex (as a process to fix a problem) only when the Adobe support instructed you to do.

Please check the official documentation regarding this: https://docs.adobe.com/content/help/en/experience-manager-65/deploying/practices/best-practices-for-...

[Nirmal_Jose]

Hi @bsr060893,
First off, why did you delete the folder index under /crx-quickstart/repository as a part of full re-index(I believe that's what you're trying to achieve). You don't have to do that even if you want to fully re-index.

Have a look at this : How to complete full re-indexing in AEM

Also, setting reindex={Boolean}true is one way to do it, but only a particular index will get re-indexed, not all of them.

Thanks, Bilal.

[Nirmal_Jose]

Removing the index folder and restarting AEM is the recommended method if lucene index binary is corrupt. Ref - https://github.com/AdobeDocs/experience-manager-65.en/blob/master/help/sites-deploying/best-practice...

Agree that oak run is the right way to do a full reindexing, but deleting the index folder and restarting should work as well.