[SERVER-63886] Add write blocking check in reverse command steps Created: 22/Feb/22 Updated: 06/Dec/22 Resolved: 22/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ali Mir | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
If write blocking is enabled, check the old source (new destination) to make sure that it still blocks writes. If it was not blocking writes, output a warning message, and block user writes on the cluster. This should be done after we transfer the resume data from old destination to new destination. This ticket is a nice-to-have, but not necessary, guardrail, and we should evaluate whether to complete it once REP-30 is closer to wrapping. |
| Comments |
| Comment by Ali Mir [ 22/Feb/22 ] |
|
Accidentally created a SERVER ticket not a REP ticket. |