[DOCS-9845] Update & Improve "Concurrency FAQ" page Created: 01/Feb/17 Updated: 30/Oct/23 Resolved: 29/Apr/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | Assignee: | Kay Kim (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 41 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
docs/source/faq/concurrency.txt needs some corrections. Currently, it isn't exact when it uses the term "lock"; sometimes an actual lock on a Database resource is meant, while other times it says "lock on the database" when it really means a document-level lock. |
| Comments |
| Comment by Kay Kim (Inactive) [ 29/Apr/20 ] |
|
Given that the page has been updated for 4.2 through other tickets, will close this. Any stragglers, I believe, can be handled via specific jira tickets. |
| 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: |
| Comment by Eric Milkie [ 01/Feb/17 ] |
|
There are also sections that are simply wrong or out-of-date that need to be rewritten or removed. Some of the sections are using terminology that only made sense prior to the release of database-level locking. |