Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-52797

Large synchrony EVENTS table leads to OOM during XML Site Backup

    XMLWordPrintable

    Details

    • Symptom Severity:
      Severity 2 - Major
    • Support reference count:
      1
    • Sprint:
      About a girl, Billie Jean
    • Testing Notes:
      • Make sure backup zip exports and imports all include synchrony data.
      • large amounts of synchrony data doesn't cause an OOME. large here means more than the max memory given to confluence.

      Description

      We use a <composite-id> type in hibernate for the EVENTS table (because synchrony has two columns as a composite id). However, hibernate treats entities with composite ids differently to entities with an id field. Specifically, hibernate when being asked what the id of an entity is (which is what we do to get a handle during export), it returns the entire entity object as the id.

      We keep around these "transient" ids in our xml export to make sure we don't duplicate etc. The code that uses these ids assume that they are small.

      We will have to re-implement it with a composite id class, and hopefully, that will fix the issue.

        Attachments

          Activity

            People

            • Assignee:
              jxie Joe Xie
              Reporter:
              bmcnamara Brendan McNamara
              Participants:
              Last Touched By:
              Katherine Yabut
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last commented:
                1 year, 39 weeks ago