[DOCS-6878] Comment on: "manual/tutorial/build-indexes-in-the-background.txt" Created: 27/Dec/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

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

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: bite-sized, docs-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.org/v3.0/tutorial/build-indexes-in-the-background/
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36
Referrer: https://www.google.com/
Screen Resolution: 1600 x 1200
repo: docs
source: tutorial/build-indexes-in-the-background


Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

Please explain WHY you see fit to lock the entire database when I am just creating an index on a single collection in the database. It makes no sense to me on the face of it.

In my use case each user of my app has a set of collections some of which are indexed. So if I add a new user at runtime then I can't build the indices for that user's collections except in background without locking my entire database and locking up the app? Why is foreground the default? It is quite dangerous.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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