Just trying to see if anyone has seen a similar observation to the ones we observe with tag operations in AEM and the impact of the garbage collector hoovering up tags with a cq:movedTo and zero reference count. We have changed the garbage collector configuration to run it every 2 mins to speed things up.
Let's say a tag goes through three move/renames such as: fruits/apple > fruits/orange > some-tag/pear
- Then fruits/apple has a cq:movedTo pointing to fruits/orange and a reference of 1 as a Page is tagged with it. At this point fruits/apple resolves to fruits/orange as you would expect it to
- fruits/orange has a cq:movedTo pointing to some-tag/pear, it also has backlinks pointing to fruits/apple.
- some-tag/pear has no cq:movedTo as it's the result of the last move/rename. It has appropriate backlinks. At this point, fruits/apple resolves to some-tag/pear as you would expect to but only until GC kicks in!
GC kicks in and hoovers up fruits/orange. The linkage across the three nodes is broken and the Page in question is not able to resolve the original fruits/apple to some-tag/pear manifesting in missing tag on Page.
Does GC true-up the moveTo properties on the original node as it goes about deleting interim nodes? If not, how are the tags at the either ends (fruits/apple and some-tag/pear in this case) are supposed to resolved? Or, perhaps, GC, in this case, should not be hoovering up fruits/orange in the first place? Has anyone seen anything like this? I'd love to know.
