[DOCS-1362] Possible to call db.fsyncLock() while profiling is enabled Created: 09/Apr/13  Updated: 16/Mar/15  Resolved: 11/Aug/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.9

Type: Bug Priority: Minor - P4
Reporter: Jeremy Mikola Assignee: Michael Paik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-1364 Documentation doesn't indicate that d... Closed
Participants:
Days since reply: 9 years, 27 weeks, 2 days ago

 Description   

The db.fsyncLock() docs say:

Note: The database cannot be locked with db.fsyncLock() while profiling is enabled. You must disable profiling before locking the database with db.fsyncLock(). Disable profiling using db.setProfilingLevel() as follows in the mongo shell...

I was able to lock a 2.4.1 database while profiling was enabled (mode 2). Issuing queries while locked resulted in no new data entering the system.profile collection, and once the DB was unlocked, profiling continued as expected.



 Comments   
Comment by Githook User [ 11/Aug/14 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-1362, removing references to necessity of disabling profiling before using db.fsyncLock()

Signed-off-by: kay <kay.kim@10gen.com>
Branch: v2.4
https://github.com/mongodb/docs/commit/8dad42e293886926e45871799c0e94419a5dbd1e

Comment by Githook User [ 11/Aug/14 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-1362, removing references to necessity of disabling profiling before using db.fsyncLock()

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/e6aa2c8a1ebdd14feed7b9a567d7faf73737ad41

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