Skip to content

Examine Index Getting Corrupt on Azure Server #19278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shaishavkarnani opened this issue May 8, 2025 · 3 comments
Open

Examine Index Getting Corrupt on Azure Server #19278

shaishavkarnani opened this issue May 8, 2025 · 3 comments

Comments

@shaishavkarnani
Copy link

Which Umbraco version are you using?

All 13 versions

Bug summary

We have setup few Umbraco Azure Projects and have used below guidelines.
https://docs.umbraco.com/umbraco-cms/fundamentals/setup/server-setup/azure-web-apps

However, one issue that we have seen consistently is that Examine gets corrupt for website that frequently fetch results and save entry to examine. Do you have any suggestion on how to fix it? We need to clean the examine folders and restart the web app to ensure it is working fine again.

I have also updated to Examine 3.7 library.

It seems internally whenever Azure auto restarts then it break examine due to some lock and either causes lot of examine files to be generated or any missing file. Leading to site downtime or any section that uses Examine goes down.

Please guide how to fix this issue.

Specifics

No response

Steps to reproduce

I think this issue is already known by Umbraco. It is sporadic.

Expected result / actual result

No response

Copy link

github-actions bot commented May 8, 2025

Hi there @shaishavkarnani!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@jpkeisala
Copy link

I am using Umbraco Cloud and I have the same issue. No logs anywhere. Examine just gets corrupted and I have to go to KUDU and delete ExamineIndexes on Umbraco/TEMP and then rebuild them to get them back. Sometimes it runs days sometimes hours. No way to reproduce it.

@rpteasolutions
Copy link

I am using Umbraco Cloud and I have the same issue. No logs anywhere. Examine just gets corrupted and I have to go to KUDU and delete ExamineIndexes on Umbraco/TEMP and then rebuild them to get them back. Sometimes it runs days sometimes hours. No way to reproduce it.

We are seeing the exact same on 13.7.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants