[SERVER-3248] autoresync - not working with replset Created: 13/Jun/11  Updated: 12/Jul/16  Resolved: 16/Jun/11

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

Type: Bug Priority: Minor - P4
Reporter: MartinS Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

mongo 1.8.1 (stable), linux 2.6.32


Operating System: Linux
Participants:

 Description   

#mongod --help
...
Replication options:
--fastsync indicate that this instance is starting from a dbpath
snapshot of the repl peer
--autoresync automatically resync if slave data is stale
--oplogSize arg size limit (in MB) for op log
...

autoresync is put in replication options, not in master/slave options so it should work with replset. Adding autoresync=true brings no effect.



 Comments   
Comment by Dwight Merriman [ 14/Jun/11 ]

there is a different process to get back in sync with replica sets it is detailed here:
http://www.mongodb.org/display/DOCS/Resyncing+a+Very+Stale+Replica+Set+Member
will do a checkin that makes the command line help more clear.

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