Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-1879

OOM due to huge RangeSet of purgedTransactions in FrontendHistoryMetadataBuilder

XMLWordPrintable

      Submitting a great mount of ReadOnlyTransaction and WritingTransaction in turns causes OOM.

      We think it is the transaction id of ReadOnlyTransaction that splits the purged transaction range into lots of segments.

        1. Clip(12-12-13-42-56)(9).png
          Clip(12-12-13-42-56)(9).png
          82 kB

            tcere Tomas Cere
            zhfinder Huafei Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: