Confusing log entry in regards of the examine index rebuilding

[wtct]

Which Umbraco version are you using?

13.9.2

Bug summary

We noticed that a confusing log entry appears while the index rebuilding is triggered in the Examine Management dashboard.

It occurs only if there is more than 10K of documents to index in the system.

Basically, once you trigger the index rebuilding for the Internal or External index, you can expect an entry as below while the first 10K of documents have been indexed:

Rebuilding index '"InternalIndex"' done.

Unfortunately, you can notice that process is still running in the background. You can confirm that by checking the DocumentCount in the overview of the index in the Examine Management dashboard.

Probably the same issue occurs once the examine index rebuilding is automatically triggered on the application startup.

You can find details in our article: Umbraco Examine Rebuild Says "Done" – But It’s Not

cc: @piotrbach

Specifics

No response

Steps to reproduce

1. Go to the Examine Management dashboard in the Umbraco instance with at least 10K of documents to be indexed in the examine internal or external index.
2. Trigger index rebuilding in the Examine Management dashboard.
3. Keep refreshing the index overview in the Examine Management dashboard to ensure the DocumentCount is increasing during indexing.
4. Check Umbraco logs while at least 10K of documents have been indexed.
5. Refresh the index overview page several times to see that the the DocumentCount is still increasing.

Expected result / actual result

Actual result

The index is still being populated even you can see the log entry as follows:

Rebuilding index '"InternalIndex"' done.

Expected result

The log entry should appear while the rebuilding process has been completed successfully.

[github-actions]

Hi there @wtct!

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 🤖 🙂

[kjac]

Hi @wtct

Thanks for reporting this. Incidentally, this is implicitly solved by #20543 for V17.1 - moving forward we won't be logging this at all. Instead, the long running service tracking should be utilized to keep track of index rebuilds.

See details on the how's and why's on the linked PR.

Since the long running service implementation is not a part of V13, unfortunately we won't be porting this back to V13.