[SERVER-76309] Re-enable support for high water mark tokens in serverless Created: 19/Apr/23 Updated: 24/Apr/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mickey Winters | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
during PM-2341 in |
| Comments |
| Comment by Mickey Winters [ 24/Apr/23 ] |
|
the previous mechanism would send a new hwmt when another tenant does a write which is an issue for shard split. so this needs to be redone to look at the last timestamp in that tenant's change collection instead of the last event in the oplog. the last timestamp in the oplog is problematic because if there is a split a non migrating tenant can do writes during the critical section and a migrating tenant might wind up with a resume token with a time stamp after the split operation's blockTS |