Index rebuild

This should work, but I'd say contact Kentico support with the exact Version and hotfix version you're using. And I assume this is for a custom search index? (include that as well!). They can pretty quickly tell you if this is fixed in a specific hotfix...

First thing to understand here is when something is updated, the index updates itself, not rebuild. That's why when you go to the index in the Smart Search application, you will see 2 time stamps, last update and last rebuild.

Content updates via content staging would trigger index update automatically. If it's not updating, then you should look at the PROD > Smart search > Tasks, are there index tasks stock in there? Is the PROD index updating if you make an update directly? Are you using web farm in PROD?

Hi Rui,

We are not using web fram. We saw that our clients using amazon s3 storage for storing indexes. We asked them to check any .lock files in amazon storage. They checked and deleted the existing .lock file and indexes rebuild successfully.

But again after two days, the problem again came into picture. So the .lock files are creting too frequently. Could you please shed some light why the .lock files are creating too frequently?

Hi Srikanth, that's different than the initial questions.

You can take a look at this article https://devnet.kentico.com/articles/troubleshooting-smart-search-with-external-storage

Specially the first, third and fourth points.

Hi Rui Wang,

I appreciate your link provide regarding .lock files and its clean up.

May I know what are the possible reasons .lock files are getting created but not deleted?

We have the same configurations (Amazon s3) in two environments. In one environment(QA) it is working great but not in the other environment(stage/prod).

Please suggest.

Thanks, Naresh

@Naresh this would be a suitable case for our support team to handle. You can email them at support@kentico.com and ask the question.