[DOCS-11871] Steps to rollback from CSRS to SCCC Created: 12/Jul/18  Updated: 29/Oct/23  Resolved: 12/Oct/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: 3.2.20
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Linda Qin Assignee: Isabella Siu (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 5 years, 17 weeks, 2 days ago

 Description   

----------------------------

Original Description

Currently we have the documents to upgrade from SCCC to CSRS. However, we don't have a full document on downgrading from CSRS to SCCC.

Some steps are documented in the downgrade document (downgrade from 3.2 to 3.0) - Prepare CSRS Config Servers for downgrade. However this is not a complete list. It would be nice if we can document the full steps. The steps look like:

  1. Disable the Balancer..
  2. Check the minOpTimeUpdaters value..
  3. Prepare CSRS Config Servers for downgrade..
    • If there is any requirement to rollback to the original servers/MMAPv1, after all the nodes in the cluster are stopped in Step c and before Step d to start the SCCC members, dump the config database from a CSRS member (running on standalone mode) and restore to the SCCC members with --drop option.
  4. Clear per-shard sharding recovery information..
    • Note that if the cluster is running with authentication enabled, it's needed to grant the proper privilege to the administrator user, in order to remove the minOpTimeRecovery document from the admin.system.version collection. Please replace USER with the proper administrator user.

      use admin;
       
      db.createRole({
        role: "downgrade_csrs",
        privileges: [
           { resource: { db: "admin", collection: "system.version"}, actions: [ "remove" ] },
        ],
        roles: [  ]
      });
       
      db.grantRolesToUser("USER", ["downgrade_csrs"]);
      

  5. Restart all the shard mongod instances.
  6. Start the mongos pointing to SCCC
  7. (Optional) The local database can be drop from the SCCC members if exists.

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Githook User [ 15/Oct/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: fix build error from DOCS-11871
Branch: master
https://github.com/mongodb/docs/commit/9533554400051f1a3e2ced2d96383b8546d380de

Comment by Githook User [ 12/Oct/18 ]

Author:

{'name': 'iwysiu', 'email': 'sakurablossom@blueblueworld.com', 'username': 'iwysiu'}

Message: Merge pull request #3446 from iwysiu/DOCS-11871

DOCS-11871 edit steps to rollback from CSRS to SCCC
Branch: master
https://github.com/mongodb/docs/commit/12395f8630c99e7559dd909576809f771a1e7159

Comment by Githook User [ 12/Oct/18 ]

Author:

{'name': 'Isabella Siu', 'email': 'isabellasiu@Isabellas-MacBook.local'}

Message: DOCS-11871 edit steps to rollback from CSRS to SCCC
Branch: master
https://github.com/mongodb/docs/commit/2f452481210a967356e9b10405371bc20965a31b

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