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

OOM due to huge RangeSet of purgedTransactions in FrontendHistoryMetadataBuilder

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          split to

          Bug - A problem which impairs or prevents the functions of the product. CONTROLLER-1991 Tell-based protocol can leak transaction IDs on the backend

          • High - Serious problem that could block progress.
          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: