[SERVER-41894] Use the same registerChange logic for ephemeralForTest as other storage engines Created: 24/Jun/19 Updated: 06/Dec/22 Resolved: 08/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | intern_ephemeral_for_test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
ephemeralForTest should be modified to use the generic RecoveryUnit registerChange logic. |
| Comments |
| Comment by Gregory Wlodarek [ 20/May/20 ] |
|
We should be able to close this after PM-1244 |