Once in a while, the Commerce Seach Index Processer ends up in state closed. We are seing this in both development and testing environments. In these situations, it is not possible to Build or Rebuild the index. Clicking on the Validate and Invalidate buttons does not change anything.
What does state Closed mean, and how do we get the processer out of this state?
An iisreset changes the state, but that is not a very attactive option in production (which we haven't reached yet).
I've met the same.
Does anybody now what Closed state means?
I have received no reply to this thread, so I have created an EPiServer Support case yesterday.
Do you have any updates on this?
No, unfortunately not. I did get in touch with EPiServer Support, but they asked for more help on recreating the problem and in logging information. Unfortunately I can't reliably reproduce the issue, so I haven't been able to provide the needed information to EPiServer support, and I haven't had the time to look that much into the problem. This means that my support case was closed again.
If you can reproduce the problem reliably, I suggest that you create a new support case to EPiServer.
We're also experiencing this a lot. It *seems* to be every time we import new products programatically, that the index is suddenly invalid and needs to be rebuilt. But I don't know for sure what causes it, and - as you - we can't reliably reproduce it.
Shouldn't this index have a triggered update when updating things when using IContentRepository - or is this already handled?
Which version are you using?
There was a bug in Commerce when you change create a node, all catalog entries will be re-indexed: http://world.episerver.com/support/Bug-list/bug/121067
This was fixed in 8.9 release.
Ah, we just recently upgraded past 8.9, so then it might have been fixed. I'll try to keep this thread updated if I notice anything new.