LINKS table very large and application index cannot re-build

[Dragon Moon]

Hello, we have a Confluence DB that is about 11GB of data and the LINKS table is about 7GB of data. We have over 50 million LINKS but only 53K CONTENT rows. Some content ids have several million links associated with them. I believe this is why our index rebuild is not finishing. Is there any safe links cleanup we can do?

Thanks!

[Michael Katze _ Trivadis Germany GmbH]

Hello,

same case of the problem here!

I'm supporting a Confluence installation that contains over 5 million entries in LINKS table, but only about 30.000 entries in CONTENT. I've never seen this relation befor.

The re-index is working fine on this installation. But the XML export is absolutely  useless with default settings.
I need to give tomcat 8GB of memory to prevent a crash. - And than it still needs over 2h! to export to XML (without attachments!).

Now the question is: Where are all these links comming from?
And i have the same question as @Dragon Moon: "Is there any safe links cleanup i can do?"

[hsuhailah]

Did it hang at certain percentage? There are few possibilities why index is failing/not completed and it includes the followings but I'm not too sure if LINKS has something to do with it and it also depends on what was thrown in <confluence-home>/logs/atlassian-confluence.log:

• https://confluence.atlassian.com/display/CONFKB/Confluence+Fails+to+Rebuild+Index+and+Hangs
• https://confluence.atlassian.com/pages/viewpage.action?pageId=218270911
• https://confluence.atlassian.com/display/CONFKB/Manual+Index+Process+Hangs+at+99+Percent+and+Index+Queue+Fails+to+Flush
• https://confluence.atlassian.com/display/CONFKB/Confluence+Fails+to+Process+Index+Queue+Automatically

What error can be seen in the logs related to index?