[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: |
| Comment by auto [ 01/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 01/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| 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: |
| 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 |