Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53831

Force SpiderMonkey to garbage collect in ReplSetTest.checkOplogs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0, 4.2.13, 4.4.5, 4.0.24
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2, v4.0
    • Sprint:
      Repl 2021-02-08
    • Linked BF Score:
      7

      Description

      Certain tests, like the backup_restore_*.js tests, set a large oplog size. If the oplog becomes large (especially if there is a concentration of particularly large entries), SpiderMonkey can cause an OOM when checking the oplogs. This should be able to be fixed by manually having SpiderMonkey garbage collect (at least if the oplog is large), which is what the itcount function currently does to avoid this issue.

        Attachments

          Activity

            People

            Assignee:
            jason.chan Jason Chan
            Reporter:
            gregory.noma Gregory Noma
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: