Deleting the Journal IDs on Nodes will cause Indexing to run on restart

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.



Problem

If you clear the Journal folder on restart in your Confluence Data Center instance, then the system will perform a full re-index on every restart. This is not desirable in large enterprise installations where the Content Indexing process may take many hours to complete.

Diagnosis

After every restart of a node, Confluence will immediately being reindexing content within the application. This is contrary to expectations, as the Data Center nodes should not be reindexing on restart unless the instance was performing a full rebuild of the indexes from scratch.

Cause

If the edge_index.id and main_index.id are deleted from the journal folder in the Confluence Home directory, then the two nodes will not share the same journal ID for the indexes. If the IDs do not match between the nodes, then the instance will begin a complete content reindex to restore the parity between the nodes.

Resolution

To resolve this issue, do not remove the contents of the journal directory in your instance.


Last modified on Feb 5, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.