Hi All,

We've investigated this issue with the reporting engineer and have been unable replicate it or find cause for the behaviour.

The issue was opened whilst the other duplicate content bugs discussed in Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community were unpatched, and we believe it is likely that one of these other bugs caused the behaviour.

Supporting that conclusion is that we used the hard eviction function to replicate the issue we saw in CONFSERVER-69074: Duplicate Content Shown When Editing A Page After Modifying An Attachment (fixed in Confluence Server and Data Center 7.15.0, 7.4.15, 7.13.4), so it's wholly possible the hard eviction consideration is a step in the problem, rather than a primary driver.

As development and support have been unable to replicate the issue, we're going to go ahead and close this out, however we'll revisit the issue if we encounter any reports with associated Collaborative Editing Feedback Tool files.

b2503393acb9 - Can you please review the information at Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community. It lists a number of ways this issue can present after the fix is implemented.

We'll continue to keep an eye out for these issues, so if you're able to capture duplication at the time it occurs, please capture a report for us to investigate.

Thanks,
James Ponting
Engineering Manager - Confluence Data Center

We just had the same issue with a page just getting a copy of itself added at the end. As this is still open its hard to track where and how this occured otherwise than this bug.

Hi 78c376adccc5,

This particular bug requires the administration team to manually trigger a maintenance task in Confluence to cause the issue, so I suspect you may be seeing a similar but different issue.

We're currently working on a similar series of bugs that could be related. I'd suggest reviewing the first link below, and keeping an eye on the second

1. Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community as it serves as a single source for information for customers seeing duplicated content
2. CONFSERVER-69074: Duplicate Content Shown When Editing A Page After Modifying An Attachment (fixed in Confluence Server and Data Center 7.15.0, 7.4.15, 7.13.4)

Hopefully this is of some help.

Thanks,
James Ponting
Premier Support Engineer

Hi all, this is impacting all of our users on a random basis.

Please investigate and fix ASAP.

Thanks,

Kathryn Reddie
Confluence Admin
DHA
Australia

Hey b03c514954d7,

We would hope that customers wouldn't have the hard eviction job enabled. As you observed, it's a disruptive task.

I can confirm the soft eviction job doesn't cause this issue as it isn't as aggressive in how it cleans up data (by design). The soft eviction job should be more than enough to keep Confluence healthy, but the hard eviction job can be useful in some limited cases. I wouldn't recommend running it unless suggested to by Atlassian Support.

We've recently seen a flurry of people watching this issue since I mentioned it in the community post you've linked to. As a result, the priority of the bug has gone up inline with our Atlassian Data Center and Server Bug Fix Policy.

We'll continue to monitor this and other bugs, but I would expect this will be the lowest priority of the set as it's the least likely to occur.

Thanks,
James Ponting
Premier Support Engineer

It would appear that all the other bugs referenced in Confluence Server and Data Center: Content duplication fix and next steps are closed, including CONFSERVER-59227 .

After reading How to remove Synchrony data,  I'm wondering just how often folks have the hard synchrony data eviction job enabled. Sounds pretty intrusive and disruptive in a busy/active system.

If it's true that soft eviction isn't affected and the use of hard data evication is legitimately a corner case, it might support the lower priority of this issue.

I couldnt agree more to the previous comments either.
Anything that impact the data should be adressed asap.
As long as this concerns me - this is a higher priority issue than it evaluation!
This is bad, really bad.

I could not agree more to previous sentiments on this - and maybe a timing issue, but the related issue https://jira.atlassian.com/browse/CONFSERVER-59227 now has "highest" priority.

For good reasons, because the main use case for using Confluence is collaboration - that said, editing in a group causing unnecessary data volumes, slowing things down, means bad impact on the primary use case. Atlassian, please make sure to take this on with all you have. Thank you. 

This is very very bad problem for us. So much content to keep eye on and it will go so far that it cannot even load some pages - timeout error. I am thinking of disabling synchrony, but this is something our users are used to now.

Just want to verify that any time you re-enable Collaborative Editing mode, even after disabling it and Synchrony Data Removal (Hard), this issue re-appears.  I would propose that this is more than a minor issue – I can't use Collaborative Editing without entire page contents being duplicated frequently, and with no fix outlined to resolve this issue at all while maintaining collaborative editing.

Version 7.8.1