[SERVER-580] configurable slave delay Created: 27/Jan/10  Updated: 12/Jul/16  Resolved: 01/Mar/10

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

Type: Improvement Priority: Critical - P2
Reporter: Eliot Horowitz (Inactive) Assignee: Aaron Staple
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by auto [ 01/Mar/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-580 try to remove windows warning
http://github.com/mongodb/mongo/commit/ee3e5923e55f419a8d0fc144cc6251d432421563

Comment by auto [ 01/Mar/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-580 implement slavedelay
http://github.com/mongodb/mongo/commit/bdeca98185ef9b47af20f3fb8e557546f9466d44

Comment by auto [ 01/Mar/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-580 add putBack() to db client cursor
http://github.com/mongodb/mongo/commit/218036b2a46b8bed6f46145c3b10c176f47a2b8f

Comment by Aaron Staple [ 01/Mar/10 ]

The repl code uses a DBClientCursor to iterate through a master's oplog. It would be convenient to have a putBack() function in DBClientCursor so that when I find an op that is too fresh I can just backtrack. Does putBack() sound reasonable?

Comment by Eliot Horowitz (Inactive) [ 26/Feb/10 ]

Aaron:
Dwight and I think the easiest/fastest way to implement this is to sleep when you get an op from the log that is too fresh.
You can pause for the exact amount of time until you're allowed to apply that op.
Since ops are in order, this should be totally consistent.
bumping to 1.3.4 as that should be a very simple change

Comment by Kenny Gorman [ 26/Feb/10 ]

This will help enterprise adoption. Operations folks are always saying "what if there is a code push that causes logically corrupt data". Delayed slaves solves this problem for the most part.

Comment by Eliot Horowitz (Inactive) [ 25/Feb/10 ]

if this is easy, lets bump to 1.3.4

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