edge_index journal file stopped updating after upgrading to Confluence 7.17 or newer
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
The edge_index file is part of the journal service that keep tracks of the changes made in Confluence (in specific, Likes and Popular Contents), this file holds the value of the latest indexed entry ID and will get updated over time as the index progress.
After upgrading to Confluence version 7.17, the edge_index stopped updating itself, despite the rest of journal files in the <local-confluence-home>/journal folder (such as change_index and main_index) are working as expected.
ℹ️ If you are installing a new Confluence 7.17 or newer, you will not find the edge_index file in the <local-confluence-home>/journal folder.
Diagnosis
Environment
Confluence 7.17 or newer
Diagnostic Steps
While starting up Confluence, you will notice the following error in the
atlassian-confluence.log:1 2 3 4 5 62022-09-07 14:04:11,749 WARN [Catalina-utility-1] [confluence.impl.index.DefaultIndexRecoveryService] isIndexRecoveryRequired index recovery required! journal entry 2689875 not found for for edge_index 2022-09-07 14:04:11,749 WARN [Catalina-utility-1] [confluence.impl.index.DefaultIndexRecoveryService] triggerIndexRecovererModuleDescriptors Index recovery is required for edge index, starting now 2022-09-07 14:04:11,937 WARN [Catalina-utility-1] [confluence.impl.index.DefaultIndexRecoveryService] recoverIndexFromSharedHome unable to find entry 2689875 in the journal, journal_id is not up to date 2022-09-07 14:04:21,975 WARN [Catalina-utility-1] [confluence.impl.index.DefaultIndexRecoveryService] recoverIndex Timeout waiting for index recovery, no other nodes responded to offer their index snapshot within 10 seconds. To increase this, modify the system property 'confluence.cluster.index.recovery.query.timeout' where the time unit is in seconds. 2022-09-07 14:04:21,975 WARN [Catalina-utility-1] [confluence.impl.index.DefaultIndexRecoveryService] triggerIndexRecovererModuleDescriptors edge failed to recover, attempt 1/1 2022-09-07 14:04:21,975 WARN [Catalina-utility-1] [confluence.impl.index.DefaultIndexRecoveryService] triggerIndexRecovererModuleDescriptors Could not recover edge index, the system will attempt to do a full re-inde
Cause
This behavior is caused by a bug as reported in CONFSERVER-79953 - "Could not recover edge index, the system will attempt to do a full re-index" message on atlassian-confluence.log is causing confusion.
Despite the error message and the edge_index journal file not being updated in the file system, the actual edge index should still be intact, please refer to the section below for verification steps.
Solution
Workaround
To verify if the actual edge_index is still intact, please run the two queries below in your Confluence database:
1
2
3
select * from bandana where bandanakey='edge_index';
select max(entry_id) from journalentry WHERE journal_name='edge_index';The value return for both queries should be close, if not the same. Otherwise, please attempt to rebuild your edge_index by accessing <confluence-url>/plugins/servlet/edge-index/build
Resolution
The bug causing this behavior is currently tracked via CONFSERVER-79953 - "Could not recover edge index, the system will attempt to do a full re-index" message on atlassian-confluence.log is causing confusion, please upgrade to the fixed version as stated in the bug report to resolve the issue.
Was this helpful?