[SERVER-6536] How to convert existing Hidden Secondary to Delayed member for Disaster Recovery Created: 20/Jul/12  Updated: 15/Aug/12  Resolved: 20/Jul/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.0.5
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Sunil Ghanta Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux x_86_64


Participants:

 Description   

Each Shard in our Cluster has one Hidden Secondary in DR site.
My question is how to convert Hidden Secondary to Delayed Member ( by 2 hours). Hidden members are in Sync with Master now.
Please provide the procedure. Do you see any impact/issues while converting Hidden member to Delayed member?



 Comments   
Comment by Scott Hernandez (Inactive) [ 20/Jul/12 ]

The docs are here for configuring replica set members: http://www.mongodb.org/display/DOCS/Replica+Set+Configuration#ReplicaSetConfiguration-AdvancedConfigOptionalArguments

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