Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
*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
*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
-
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.