[DOCS-657] Docs don't cover some details regarding ensureIndex() Created: 25/Oct/12  Updated: 30/Oct/23  Resolved: 08/Nov/12

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

Type: Improvement Priority: Minor - P4
Reporter: William Zola Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 11 years, 14 weeks, 6 days ago

 Description   

The documentation doesn't cover the following about the behavior of ensureIndex():

  • What happens when multiple ensureIndex commands are run at the same time. (Answer: if there is no index present, the first will create the index entry in the system.indexes collection, and the rest are no-ops.)
  • Noting that all ensureIndex() does is put an entry in the 'system.indexes' collection, which immediately kicks off the index build operation
  • Noting that there is no way to interrupt an index build once it has begun
  • Emphasising that all other operations will block while an index build is in progress


 Comments   
Comment by auto [ 08/Nov/12 ]

Author:

{u'date': u'2012-11-08T21:23:09Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-657 clarification of ensureIndex behavior
Branch: master
https://github.com/mongodb/docs/commit/c1e9fd2573bf6bb0f0381b7019cfa6bef0592088

Comment by Sam Kleinman (Inactive) [ 08/Nov/12 ]

adding these notes modulo background indexing capabilities.

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