[SERVER-56639] Timestamp index ident drops for startup recovery Created: 05/May/21 Updated: 29/Oct/23 Resolved: 08/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Wlodarek |
| 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: |
v5.0
|
||||||||||||||||||||
| Sprint: | Execution Team 2021-06-28, Execution Team 2021-09-20 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 137 | ||||||||||||||||||||
| Description |
|
Currently, not all writes to the _mdb_catalog are timestamped. One instance of this is when we drop the ident from an unfinished index build as a part of startup recovery. However, as described in the comments of |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit cd1f82b1bde1dac9f2f5489cdc4a727fffd2a106) |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit 9661ce71f28871fc05becb9276a79a643fd2ffdf) |
| Comment by Githook User [ 09/Sep/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 08/Sep/21 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Henrik Edin [ 23/Aug/21 ] |
|
Change this ticket into improving test coverage. We keep that part as 5.1 Required. Test reading at timestamps that exercise durable history after startup recovery. |
| Comment by Daniel Gottlieb (Inactive) [ 06/May/21 ] |
|
Perhaps a useful to know caveat: non-replicated operations (such as creating a user collection on the local database, which is allowable whether a node is a primary or a secondary) must not be timestamped. Or at least not without careful consideration to the impact. |