[SERVER-53617] ephemeralForTest storage engine does not support Rollback To Timestamp algorithm Created: 06/Jan/21 Updated: 06/Dec/22 Resolved: 04/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | EFT | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
This came out of investigating the replica_sets failures after setting EMRC=true in EFT. See this patch. In rollback_all_op_types.js and rollback_ddl_op_sequences.js, we are using rollbackViaRefetch despite EMRC=true. This is because EFT does not support recoverToStableTimestamp. We need to add this support before making EMRC=true the default. |