-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
28
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
There are times that Confluence ancestor CONFANCESTORS table gets out of sync which could cause some bizarre issues.
Currently, the only way to identify this is to wait until a user hit into the above issues or any unknown upcoming issue. This is very hard to catch. And currently, one would need to rebuild it manually.
It'd be nice if the health state of CONFANCESTORS table can be identified from an accessible page in admin console or perhaps in the System Information (would be a huge win for Support).
It'd be even nicer if Confluence would automatically rebuild the ancestor table once it's detected to be out of sync or corrupted.
Workaround
Quoting from this KB - Unable to Move Pages with Attachments. This can be checked manually by running this SQL query:
SELECT A.ANCESTORID, A.DESCENDENTID, COUNT(A.DESCENDENTID) FROM CONFANCESTORS A, CONTENT B WHERE B.CONTENTID = A.DESCENDENTID GROUP BY A.ANCESTORID, A.DESCENDENTID ORDER BY 3 DESCAll returned rows should have value '1' for the column 'count'. If there is a value other than '1' (e.g. '2', '3', etc.), the CONFANCESTORS table is broken.
- is related to
-
CONFCLOUD-35040 Page move action causes database deadlock and data corruption
-
- Closed
-
-
- Closed
- relates to
-
- Gathering Interest
[CONFCLOUD-25188] Identify the health state of Confluence ancestor CONFANCESTORS table and rebuild it automatically
Jens Kasperek (Bosch GmbH) (Inactive)
added a comment - We did a rebuild of our Confancestor table 2 weeks ago. Now, we have again ~ 200 multiple entries on this table -> it is again broke 
.
Could there also be a relation to the issue of moving pages taking much time and causing deadlocks?
Jens Kasperek (Bosch GmbH) (Inactive)
added a comment - We did a rebuild of our Confancestor table 2 weeks ago. Now, we have again ~ 200 multiple entries on this table -> it is again broke .
Could there also be a relation to the issue of moving pages taking much time and causing deadlocks?
Till version 5.8.17 concurrent page moves would result into corruption of cont anchestors.
It's get fixed in 5.8.17, however regression was introduced: https://jira.atlassian.com/browse/CONF-39975
https://jira.atlassian.com/browse/CONF-39975 is fixed in 5.8.18 (in fact we released 5.8.18 only because of this single regression).
Recommendation is to upgrade to 5.8.18, although no work was done for this particular ticket, corruption caused by concurrent page move operation is not fixed.