[DOCS-533] Indicate renameCollection and renameDatabse are blocking ops Created: 19/Sep/12  Updated: 30/Oct/23  Resolved: 02/Oct/12

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Daniel Pasette (Inactive) Assignee: Ed Costello
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-7059 renamedatabase blocks Closed
Participants:
Days since reply: 11 years, 20 weeks, 1 day ago

 Description   

see: SERVER-5909 and SERVER-7059



 Comments   
Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T14:32:34-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-533 edits
Branch: master
https://github.com/mongodb/docs/commit/9ce9f7e7c531ff698b1b17303836f77a147c6593

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T14:28:07-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: DOCS-533
Branch: master
https://github.com/mongodb/docs/commit/c262523702554c00b577722c9d7774dc517aabab

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T13:53:18-07:00', u'email': u'epc@10gen.com', u'name': u'Ed Costello'}

Message: DOCS-533 minor cleanup & verification of correct locks
Branch: master
https://github.com/mongodb/docs/commit/668327afedc25463e491ca64a7ea378bfe40edc6

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T12:52:59-07:00', u'email': u'epc@10gen.com', u'name': u'Ed Costello'}

Message: DOCS-533 document blocking read, write, or global operations
Branch: master
https://github.com/mongodb/docs/commit/b76c685d827fbafb6fe4f56e09ce0fec04b7652b

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-10-02T14:21:15-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: DOCS-533
Branch: master
https://github.com/mongodb/docs/commit/64c407156b7b90e30737b08f9da61e808c85fdce

Comment by auto [ 02/Oct/12 ]

Author:

{u'date': u'2012-09-24T08:53:23-07:00', u'email': u'epc@10gen.com', u'name': u'Ed Costello'}

Message: DOCS-533 add notes/warnings to commands which block db / server
Branch: master
https://github.com/mongodb/docs/commit/6e97ac99c4965987cf52ef6b93cbb61cf16b312a

Comment by Ed Costello [ 02/Oct/12 ]

Committed, working through some merge backlog before we merge, commit is here: https://github.com/epc/docs/tree/DOCS-533-renamedatabase-blocks

Comment by Daniel Pasette (Inactive) [ 24/Sep/12 ]

Your initial pass seems fair and your interpretation correct. I think it would be good to add the warning to at least the user-facing commands. fsync demands it's own special treatment as there are some surprising behaviors there.

Comment by Ed Costello [ 21/Sep/12 ]

All of these have lockGlobally()=true and lockType = WRITE:

renameCollection global,write
dropDatabase global, write
repairDatabase global, write
closeAllDatabases global, write
convertToCapped global, write
applyOps global, write
resync global, write

fsync obtains locks but doesn't appear to set a lockGlobally() or lockType().

Am I misreading the intent of lockGlobally() and lockType?

There's a number of other commands which either don't have a lockGlobally() or set it to false but set a lockType of WRITE.

My plan is/was to add a "warning" for commands which obtain a global lock and a write lock, and a "note" for those which obtain a write lock but not global.

Comment by Daniel Pasette (Inactive) [ 21/Sep/12 ]

I think differentiating is important. Which commands besides fsync+lock will write lock the entire instance?

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