[SERVER-81176] Audit codebase where we assume that durably committed means applied Created: 19/Sep/23 Updated: 27/Sep/23 Resolved: 27/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Wenbin Zhu | Assignee: | Jiawei Yang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Repl 2023-10-02 | ||||||||
| Participants: | |||||||||
| Description |
|
E.g. Some component such as serverless shard split/merge or sharding POS service might wait for write concern and assume secondaries applied the write and consequently read from secondaries or do some work based on the assumption that secondaries updated their in-memory states. |
| Comments |
| Comment by Jiawei Yang [ 22/Sep/23 ] |
|
Audit result: |