On Jira DC, when changing requirement status on one node others nodes may still reflect the cached value

On Jira DC, when changing requirement status on one node others nodes may still reflect the cached value. The database value and the nodes indexes are correct, the problem is restricted to the cache. The cache lives for 1 day

This is the scenario:

• Multiple nodes
• Import results to node 1
• Requirements Status is correct for node 1
• Requirement Status is incorrect for node 2
• JQL Search like "Requirement Status = <VALID_STATUS>" returns the correct requirement issue, for both nodes
• Overall Requirement Coverage report shows wrong results in node 2
• Traceability Report shows correct result for all nodes