[SERVER-49834] Handle fsync and fsyncUnlock during tenant migrations Created: 23/Jul/20 Updated: 14/Dec/22 Resolved: 17/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm-1791_milestone-A | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
fsync flushes all pending writes to disk, and if "lock: true" is specified, blocks the entire mongod from accepting writes (not just a particular database or collection). fsyncUnlock allows the mongod to start accepting writes again. I don't think we need to synchronize these with tenant migrations, since they don't change the user's data. |
| Comments |
| Comment by Githook User [ 14/Dec/22 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: There are two TODO's on However, The TODO for captrunc was probably meant to be on The TODO for compact was probably meant to be on |