-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 6.0.18, 7.0.14
-
Component/s: None
-
None
-
ALL
-
In both Mongo 6 and 7 versions, I can see the "0" values below for these wired tiger concurrent ticket settings.
admin> db.adminCommand( { "getParameter": 1, "storageEngineConcurrentReadTransactions":1})
{ storageEngineConcurrentReadTransactions: 0, ok: 1 }
admin> db.adminCommand( { "getParameter": 1, "storageEngineConcurrentWriteTransactions":1})
{ storageEngineConcurrentWriteTransactions: 0, ok: 1 }
admin> db.adminCommand( { "getParameter": 1, "wiredTigerConcurrentReadTransactions":1})
{ wiredTigerConcurrentReadTransactions: 0, ok: 1 }
admin> db.adminCommand( { "getParameter": 1, "wiredTigerConcurrentWriteTransactions":1})
{ wiredTigerConcurrentWriteTransactions: 0, ok: 1 }
admin> db.adminCommand({ "getParameter": 1, "featureFlagConcurrentReadTransactions": 1 })
The document say the default value is ~128 ;however we are seeing "0" counters in both new/old names. Ideally ,it should resemble 128 which seems to be the default.
storageEngineConcurrentReadTransactions
Changed in version 7.0.
Available for mongod only.
Type: integer
Default: 128
Starting in MongoDB 7.0, if you set storageEngineConcurrentReadTransactions to a non-default value, it disables an algorithm that dynamically adjusts the number of concurrent storage engine transactions.
When I changed it to 128 the new, the new changes reflected fine.
admin> db.adminCommand( { setParameter: 1, wiredTigerConcurrentReadTransactions: 128 } )
{ was: 0, ok: 1 }
admin>
admin> db.adminCommand( { "getParameter": 1, "wiredTigerConcurrentReadTransactions":1})
{ wiredTigerConcurrentReadTransactions: 128, ok: 1 }
admin> db.adminCommand( { "getParameter": 1, "storageEngineConcurrentReadTransactions":1})
{ storageEngineConcurrentReadTransactions: 128, ok: 1 }
Could you please verify this ? Also, in 6.0 its not clear whether the "0" is for dynamically managing the tickets or not or in both 6&7, 128 is the default/recommended.