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

Allow for possibility of JS interrupt in mr_bigobject_replace.js

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Linked BF Score:
      19

      Description

      The test allocates a lot of memory inside the JS execution engine. On some of our testing platforms this can take a long time. I think the best solution is to account for the possibility of the JS being interrupted because this takes too long. I also considered increasing the timeout value during this test.

      I could also see an argument that the test should be deleted since the assertion here is just testing that we apply the validation on insert - it's not really specific to javascript or mapReduce. I think it's worth having coverage for creating an object in JS larger than the limit nonetheless, and also to ensure we don't ever go through some internal backdoor which circumvents this limit.

        Attachments

          Activity

            People

            Assignee:
            charlie.swanson Charlie Swanson
            Reporter:
            charlie.swanson Charlie Swanson
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: