unbounded memory growth during tenant migrations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 6.1.1, 6.2.0-rc3, 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.2
    • Hide

      git am the attached patch.
      Then run the attached script via:
      nohup buildscripts/resmoke.py run t.js
      Observe the memory growth (or even process OOM-killed)

      Show
      git am the attached patch. Then run the attached script via: nohup buildscripts/resmoke.py run t.js Observe the memory growth (or even process OOM-killed)
    • Server Serverless 2022-12-12
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      It appears that there is no backpressure between reading from a donor and writing on a recipient; there is an in-memory buffer that lives on the recipient that tenant migration writer threads pull from to perform writes. This buffer can grow without bound if writing on the recipient is significantly slower compared to reading on the donor.

        1. 0001-memory-leak.patch
          1 kB
        2. t.js
          3 kB

            Assignee:
            Suganthi Mani
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: