[DOCS-7395] FAQ comment on yielding and wt is incomplete Created: 10/Mar/16 Updated: 26/Jul/18 Resolved: 06/Apr/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 44 weeks, 6 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
https://docs.mongodb.org/manual/faq/concurrency/#does-a-read-or-write-operation-ever-yield-the-lock For WT, as suggested by the comment there there is no need to yield in order to avoid holding locks for too long as with mmapv1. However we do yield periodically in order to avoid long-running WT transactions because a long-running transaction can potentially require holding a large amount of data in memory. |
| Comments |
| Comment by Githook User [ 06/Apr/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 06/Apr/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |