I'm using the Episerver.Find.Commerce to index my Commerce site, but I only get product and variations in one language.What am I missing?
The index has all the existing languages included and there are a lot of products and variations translated but still there is no sign of them in Find index. I have also set up two local sites under Manage Websites. One for english and one for swedish and they are nicely showing products and variations in the right language.
Am I missing some configuration maybe?
Are all the required languages enabled in the Catalog? (Can be set on the root node in catalog view).
Yes they are. And the funny thing is that when I publish a variant the index in populated with variations in all languages. Strange!
Huhm.. Weird. Are they explicitly published in all languages, or just published in one language and then translated+saved (but not properly published)?
If that's not the issue either, I'd notify support about this. Seems like strange behaviour.
So this is confirmed to be a Dxc/Azure problem. If you have a lot of items the scheduled cannot be run in the Azure environment. For some reason the site restarts after a while and the indexing crashes. Maybe the scheduled task takes up to much memory or somthing?If you try to index same site with same database and same Find index on a stand alone server it works just fine.
The Episerver Find team is looking into this as we speak.
We have an update on this one.
The pageCacheSlidingExpiration is set to 12 hours per default. As a test after a tips from Episerver we set it to just 10 minutes and suddenly the job completes in the Azure environment.I guess setting the cache to 10 minutes instead of 12 hours will slow down the performance on the site, but I don't know if we will notice? I guess we will find out.
@Quan, any input on this and what do you think about how it will afftect the performance?
Technically pageCacheSlidingExpiration - as its name suggests, has sliding expiration, so if it's requested quite frequently, it should remain in cache. If something is requested infrequently, like every 15 minutes, then it will be slower in such cases, but that would not be a problem.
In upcoming CMS 11 I heard the scheduled jobs will have more fine-tuned cache management, so for things that are loaded specifically for the job, you can configure so they will be short lived in cache (or even non cached at all). I would suggest to keep an eye on CMS 11 and try if that solves your problem completely.
P/S: how did you know you I will be looking at your post?