I am using TarMK with SP2 and Hotfix 5779 (oak: 1.0.11)
I have a custom index /content/site/oak:index/custom-index
When I request a re-index all documents are present. But roughly a day later the documents are gone again. What backend process would I need to watch out for?
Any help greatly appreciated, we are using this already in production.
Solved! Go to Solution.
Views
Replies
Total Likes
I raised a daycare ticket too but thought of posting here too just in case someone has seen this before.
It only happens on the publishers. Perhaps the index gets overwritten when we activate? Is it the TarOptimisation? I don't know.
Views
Replies
Total Likes
can you also open a support ticket as you are saying its a production issue.
Will try out myself and see if I am facing the same issue and if I could find anything to stop it.
Views
Replies
Total Likes
I raised a daycare ticket too but thought of posting here too just in case someone has seen this before.
It only happens on the publishers. Perhaps the index gets overwritten when we activate? Is it the TarOptimisation? I don't know.
Views
Replies
Total Likes
I have reasons to believe that it's related to the activation that happens on a page /content/sitea underneath which the oak:index lives. I've explicitly excluded that node from replication now and haven't seen it again, but would be good to get confirmation that the oak:index/specific-index shouldn't be activated.
Cheers, K
Views
Replies
Total Likes
Agreed - this is beyond a community issue - open a ticket if you are seeing this behaviour.
Views
Replies
Total Likes
Views
Likes
Replies