[SERVER-15066] --setParameter syncdelay doesn't work in 2.6 Created: 28/Aug/14  Updated: 06/Dec/22  Resolved: 14/Sep/18

Status: Closed
Project: Core Server
Component/s: Admin, MMAPv1
Affects Version/s: 2.6.0
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Linda Qin Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Storage Execution
Operating System: ALL
Steps To Reproduce:
  1. Start mongod with --setParameter syncdelay=1
  2. User mongo shell connect to this node, and check the syncdelay parameter, it shows the default option.

    > db.adminCommand({getParameter:1,syncdelay:1})
    { "syncdelay" : 60, "ok" : 1 }

Participants:

 Description   

This option works in 2.4, but not in 2.6.



 Comments   
Comment by Daniel Pasette (Inactive) [ 28/Aug/14 ]

you can work around by not using the setParameter form.

./mongod --syncdelay=2

Generated at Thu Feb 08 03:36:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.