Implement mechanism for providing JS_GC_ZEAL only on mongod process

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As part of our plan for monitoring and investigating the sporadic heap corruptions in SpiderMonkey (https://jira.mongodb.org/browse/SERVER-89758 ) , we would like to perform more rigorous garbage collection stress testing. 

      https://jira.mongodb.org/browse/SERVER-91111 enables a new build variant on evergreen which toggles the spider-monkey-dbg mode, and further, allows us to specify JS_GC_ZEAL settings as an environment variable to resmoke.py. 

      Unfortunately, using the environment variable method for resmoke means that both the mongo (shell) and mongod process inherit the JS_GC_ZEAL setting, and makes the test runtime too long (over 5 hours) with more rigorous zeal settings.

      As part of this ticket, provide a way to provide the JS_GC_ZEAL parameter setting only to mongod when running the evergreen build variant. The hope is that by doing this, we we will be able to run a wider variety of the GC zeal settings without timing out on the CI infrastructure. 

            Assignee:
            Santiago Roche
            Reporter:
            Santiago Roche
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: