[SERVER-680] replication --only broken on master and slave Created: 26/Feb/10  Updated: 12/Jul/16  Resolved: 26/Feb/10

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

Type: Bug Priority: Critical - P2
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Two problems with --only mode:

1) On the master, the "finding start" mode scanning doesn't work correctly when an "ns" field is specified in the oplog query.
2) On the slave, when a fresh slave is created the last oplog entry is saved for syncedTo regardless of the ns for that op.

These issues have been addressed in the v1.2 branch with
de365ac8eb96572003bd158d098916272b68eb75
1d82d20390804309258cd6d8fffd7f62c4accce6

The --only option should not be used unless both master and slave have the fix in place.



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

nope - all set
resolving and assigning to you for record keeping

Comment by Aaron Staple [ 26/Feb/10 ]

Should be done. Leaving it open in case you want to do anything administrative with it.

Comment by auto [ 26/Feb/10 ]

Author:

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

Message: SERVER-680 fix issues with --only mode
http://github.com/mongodb/mongo/commit/12544983bc7810a9d04f9e5e42691d29f2e6b300

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