Search indexes are not rebuilding when configured to Amazon S3 file storage

Srikanth Kumar asked on October 27, 2017 09:22

Hi,

Our client project ( Kentico 10 no hotfix) is configured to use Amazon s3 file storage. When we added some excluded content to our custom index, it is not rebuilding at all. Always going to Tasks section when we rebuilding and it is still in there since months. So we can't able to use smart search functionality in the site.

If we check for the smart search index files in folder "App_Data/cms_modules/smartsearch" there is no index files including those by kentico like "corporate_user" indexes. In one of the articles i saw that the indexes will store in the above mentioned location. Please help.

Thanks

Recent Answers


Juraj Ondrus answered on October 27, 2017 10:45

Hi, could you please check and follow this article? Most common issue is the deployment of the index files folder. It should be excluded from the deployment when deploying to Amazon.

0 votesVote for this answer Mark as a Correct answer

Srikanth Kumar answered on October 27, 2017 11:32

Hi Juraj,

I have a question. Are the index files will store in Amazon file storage or in "App_Data/cms_modules/smartsearch" folder, if we configured amazon storage s3.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on October 27, 2017 11:35

The index files should be stored in ~/CMS/App_Data/CMSModules/SmartSearch - that's why you need to exclude them from deployment, so they are not stored on the amazon storage.

1 votesVote for this answer Mark as a Correct answer

Srikanth Kumar answered on October 27, 2017 12:13

Hi Juraj,

Instead of that shall we delete the existing folders from smart search folder and rebuild the index again? We don't have any .lock files here. Image Text

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on October 27, 2017 12:21

I would delete the files and folders mentioned in the article from the deployed project. Then exclude them from deployment and re-deploy the project again.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.