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

Add server parameter maxTransactionLockRequestTimeoutMillis test

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-06-04

      Add the following JS test once SERVER-31767 is committed.

      jstests/noPassthrough/maxTransactionLockRequestTimeoutMillis_serverParameter.js

      // Tests the maxTransactionLockRequestTimeoutMillis server parameter.
      
      (function() {
          'use strict';
      
          load("jstests/noPassthrough/libs/server_parameter_helpers.js");
      
          // Valid parameter values are in the range (-infinity, infinity).
          testNumericServerParameter("maxTransactionLockRequestTimeoutMillis",
                                     true /*isStartupParameter*/,
                                     true /*isRuntimeParameter*/,
                                     0 /*defaultValue*/,
                                     30 /*nonDefaultValidValue*/,
                                     false /*hasLowerBound*/,
                                     "unused" /*lowerOutOfBounds*/,
                                     false /*hasUpperBound*/,
                                     "unused" /*upperOutOfBounds*/);
      })();
      

      It should have gone in with SERVER-33244, but the helper library to make the test a breeze to write is introduced in SERVER-31767, so I just made sure it worked but didn't commit it with SERVER-33244.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: