[DOCS-16038] [C2C] Document how to allow c2c source cluster to accept writes again after using enableUserWriteBlocking is set to true Created: 13/Apr/23  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: C2C
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Ivan Grigolon Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 43 weeks ago

 Description   

TODO: Fill out each section as best you can. Remove all italic template text or unused sections before submitting the issue.

Problem

When using c2c with the option 

curl localhost:27182/api/v1/start -XPOST \--data '   {      "source": "cluster0",      "destination": "cluster1",      "enableUserWriteBlocking": true   } ' 

In case you would like to allow the source cluster to accept writes again you need to run the command:

db.adminCommand({setUserWriteBlockMode: 1,global: false}) 

This is not documented in the c2c docs.

Solution & Acceptance Criteria

What should be done to complete the ticket to the best of your knowledge? If you do not know what should be done to complete the ticket, include investigating and deciding on a solution as one of the acceptance criteria.

Impact

What is the impact of the ticket being completed?

Optional Permalinks

Any relevant code, evergreen logs, commits, docs, etc. that should be included?


Generated at Thu Feb 08 08:14:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.