[SERVER-8577] Formalize/Propose Write Ordering Models Created: 14/Feb/13 Updated: 06/Dec/22 Resolved: 04/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Outcome of this task will be a document describing the consistency (write ordering) model of a standalone mongod today, a replicaset today, and a sharded cluster, today; plus, a proposal for a single consistency model that future changes to the system will maintain. |
| Comments |
| Comment by Andy Schwerin [ 04/Mar/19 ] |
|
Closing as "Done" because I believe that we did this for 3.6 and have continued to update/maintain it in the docs and the code. This includes all the work on readConcern and writeConcern we've done over the last several 5 years, since I filed this ticket. |
| Comment by Sara Williamson [ 04/Mar/19 ] |
|
We came across this ticket in storage-nyc backlog grooming and thought it made more sense for the repl team to take a look and see if this is still needed. |