CommitCount stuck and not updating

[patrickdemooij9]

Hi,

We are having an issue where the CommitCount within Examine isn't updating. We are running Umbraco 9.1.2, so that would be the latest version of Examine. (2.0.1).
We have the following information:

The commit count will just stay at that number without being picked up and put into the Examine index. If we rebuild the index, it'll keep going until the DocumentCount is 15000 and then just suddenly stop again stating that it has finished rebuilding.

This could be an Umbraco issue, but I don't see what Umbraco would be doing to cause this. We also see no errors in the logging, so we don't know if there is an error somewhere while indexing.

Kind regards,
Patrick

[Shazwazza]

That sounds like an Umbraco issue. Examine just adds data to the index that Umbraco tells it too. When rebuilding large sites like this, Umbraco will only wait a certain amount of time before telling you it's done but it might still be adding stuff to the indexes behind the scenes. If you come back after a few minutes, perhaps the count is correct.

Otherwise, it might mean that Umbraco has stopped enumerating/paging all of it's data for some reason, either query timeouts or a fault in it's paging/query logic.

[Shazwazza]

Are you able to replicate this in a different site with different data?

[patrickdemooij9]

@Shazwazza, thanks for the response! Will see if I can replicate this on a clean installation with a lot of data. Just one more question:

My understanding of "CommitCount" is that it is the number of items queued for being inserted into the indexes, so that it would slowly go down as more and more items are getting inserted. However, in this clean installation, it'll just add 22 (total amount of page) to the CommitCount every time. And it doesn't go down, even though all items are clearly indexed.

[Shazwazza]

No CommitCount is actually a legacy thing. The code comments are

/// <summary>
/// Used to keep track of how many index commits have been performed.
/// This is used to determine when index optimization needs to occur.
/// </summary>

This actually needs to be removed entirely since it's no longer used. It just tracks how many times a document is added. It in fact doesn't actually track the number of calls to Commit. The auto optimization was removed a very long time ago even in previous examine versions.