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

Reduce transactionLifetimeLimitSeconds in exit_logging.js to avoid test timeout

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • v8.0
    • Service Arch 2024-04-29, Service Arch 2024-05-13
    • 4

      --Adjust exit_logging.js to skip the dbHashes check during shard stop. This ensures a focus on crash logging testing and prevents interference in test results. Additionally, note that crashed mongos instances may leave idle transactions on shards/config servers, causing resource locks and potential hang-ups in the dbHash check process. –

      This test intentionally crashes the mongos and can make the transaction started by the ClusterServerParameterRefresher job become idle. In default, the transaction life time is 24 hours. In this case, the shard test stop operation will wait on `fsync` operation because this transaction hold for global resource lock for long time and cause the jstest timeout. We need to reduce it to less (eg, 10 seconds) to make this transaction to be quickly aborted by mongod itself.

            sophia.tan@mongodb.com Sophia Tan
            sophia.tan@mongodb.com Sophia Tan
            0 Vote for this issue
            3 Start watching this issue