[SERVER-37121] Retry timestamping secondary background index builds Created: 13/Sep/18 Updated: 29/Oct/23 Resolved: 21/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.2, 4.1.2 |
| Fix Version/s: | 4.0.3, 4.1.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Storage NYC 2018-09-24 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 5 | ||||||||
| Description |
|
Secondary background index builds may complete at any time after they start. It's important the completion is timestamped in order relative to other operations on the collection, but it's not intrinsically important what timestamp it gets (there are however some external constraints):
Of the two constraints, the first one is more sensitive to testing failures. The proposed solution is to continue to timestamp the write with the latest logical clock value, but retry (instead of fasserting) in the event the index completion lost the race with the stable timestamp. |
| Comments |
| Comment by Githook User [ 24/Sep/18 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: (cherry picked from commit 1b7b5200e158345d8818b00b039fccdccbed7aa2) |
| Comment by Githook User [ 20/Sep/18 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |
| Comment by Githook User [ 20/Sep/18 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |