[DOCS-13288] Document that sharded transactions always perform some majority writes Created: 11/Dec/19 Updated: 30/Oct/23 Resolved: 11/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 3 years, 34 weeks, 6 days ago | ||||||||||||
| Epic Link: | DOCSP-1769 | ||||||||||||
| Description |
DescriptionWe document here that sharded transactions are not allowed with writeConcernMajorityJournalDefault:false. I think it's also important to specify that regardless of the user's requested writeConcern, commitTransaction for a sharded transaction must perform some component writes with writeConcern {w: "majority", j: true. If we don't specify this, users may be confused as to why running commitTransaction with a weaker writeConcern doesn't significantly speed up their sharded transactions. (Additionally, until Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Kay Kim (Inactive) [ 11/Jun/20 ] |
|
Forgot to close |
| Comment by Githook User [ 11/Feb/20 ] |
|
Author: {'username': 'kay-kim', 'name': 'Kay Kim', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 22/Jan/20 ] |
|
Author: {'username': 'kay-kim', 'name': 'Kay Kim', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 22/Jan/20 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'username': 'kay-kim', 'name': 'Kay Kim'}Message: |