[DOCS-3916] Create stronger warning for db.foo.copyTo() Created: 18/Aug/14 Updated: 16/Mar/15 Resolved: 25/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.10 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Michael Paik | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 9 years, 25 weeks, 5 days ago | ||||||||||||
| Description |
|
References to db.foo.copyTo() should strongly caution that its use calls db.eval(), which will lock the whole mongod. |
| Comments |
| Comment by Githook User [ 22/Aug/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |