[SERVER-5706] If only slaveDelay'd nodes are available, use them Created: 25/Apr/12  Updated: 11/Jul/16  Resolved: 09/May/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.1.1
Fix Version/s: 2.0.6, 2.1.2

Type: Improvement Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-4750 Secondary syncs to another secondary ... Closed
Related
related to SERVER-5472 Uncaught exception in slavedelay3.js Closed
Participants:

 Description   

Currently the logic here (https://github.com/mongodb/mongo/blob/e4f3f956888da028bb13a469f99941537f35f272/src/mongo/db/repl/rs_initialsync.cpp#L108) will exclude slaveDelayed nodes (w/greater delays). We should do a second loop if !closest and ignore the slaveDelay check part.



 Comments   
Comment by auto [ 10/May/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-5706 if only slaveDelay'd nodes are available, use them
SERVER-4750 prevent syncing to secondaries with a slavedelay greater than yourself

Conflicts:

db/repl/rs_initialsync.cpp
jstests/replsets/slavedelay3.js
Branch: v2.0
https://github.com/mongodb/mongo/commit/1aaac5eb0dc31c80f82080c9b3e75b49409b74cd

Comment by auto [ 07/May/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-5706 if only slaveDelay'd nodes are available, use them
Branch: master
https://github.com/mongodb/mongo/commit/ffd0be5ee040354620422c01503de6b5ab31f782

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