Bump internalQueryGlobalProfilingLockDeadlineMs to avoid flaky tests

ExportXMLWordPrintableJSON

    • Query Optimization
    • Fully Compatible
    • ALL
    • v9.0, v8.3, v8.0
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Intermittent failures observed of the following form:

      [js_test:aggregation_out_on_secondary] d20291| 2026-09-10T05:05:55.587+00:00 W  -        20703       [conn12] "Caught Assertion while trying to profile operation","attr":{"operation":"msg","namespace":"out_on_secondary_db.readColl","assertion":"LockTimeout: Unable to acquire IX lock on '{Database : out_on_secondary_db}' within 1ms. opId: 51200, op: profiling, connId: 0.","code":24}
[js_test:aggregation_out_on_secondary] uncaught exception: Error: [1] != [0] are not equal :
[js_test:aggregation_out_on_secondary] doassert@src/mongo/shell/assert.js:20:14
[js_test:aggregation_out_on_secondary] assert.eq@src/mongo/shell/assert.js:176:17
[js_test:aggregation_out_on_secondary] @jstests/noPassthrough/aggregation_out_on_secondary.js:58:8
[js_test:aggregation_out_on_secondary] Error: [1] != [0] are not equal
[js_test:aggregation_out_on_secondary] failed to load: jstests/noPassthrough/aggregation_out_on_secondary.js

      No indication of an actual bug, just tests occasionally not being able to acquire IX lock in time, but expecting profiling results.

      Bump internalQueryGlobalProfilingLockDeadlineMs to some larger value for testing purposes.

            Assignee:
            James Harrison
            Reporter:
            James Harrison
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: