[SERVER-61235] Cannot set wiredTigerConcurrentWriteTransactions/wiredTigerConcurrentReadTransactions without casting the value Created: 04/Nov/21  Updated: 06/Dec/22  Resolved: 04/May/22

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alex Bevilacqua Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Operating System: ALL
Sprint: Execution Team 2022-06-13
Participants:

 Description   

The wiredTigerConcurrentWriteTransactions and wiredTigerConcurrentReadTransactions server parameters can't be set via the db.adminCommand() helper directly.

For example:

MongoDB shell version v5.0.2
MongoDB server version: 5.0.2
================
MongoDB Enterprise > db.adminCommand({ setParameter: 1, wiredTigerConcurrentWriteTransactions: 256 })
{
        "ok" : 0,
        "errmsg" : "Did not consume whole string.",
        "code" : 9,
        "codeName" : "FailedToParse"
}

Casting the value to either NumberInt or NumberLong addresses this:

MongoDB Enterprise > db.adminCommand({ setParameter: 1, wiredTigerConcurrentWriteTransactions: NumberInt(256) })
{ "was" : 128, "ok" : 1 }
MongoDB Enterprise > db.adminCommand({ setParameter: 1, wiredTigerConcurrentWriteTransactions: NumberLong(256) })
{ "was" : 256, "ok" : 1 }

Note this does not reproduce in mongosh:

Using MongoDB:          5.0.2
Using Mongosh:          0.15.6
------
Enterprise test> db.adminCommand({ setParameter: 1, wiredTigerConcurrentWriteTransactions: 256 })
{ was: 128, ok: 1 }



 Comments   
Comment by Louis Williams [ 04/May/22 ]

Because this only affects the legacy shell and is not causing problems for our testing or development for server engineers, I am closing as "Won't Fix"

Generated at Thu Feb 08 05:51:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.