[SERVER-3155] --fastsync + rs.add() allows for inconsistent data Created: 26/May/11 Updated: 11/Dec/18 Resolved: 13/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gaetan Voyer-Perrault | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The attached script can be run on a single instance for ease of reproduction. Script is complex, basic premise below. Basic Repro Problem #1 Also, I have --fastsync on. Why can't I start a replica set with known good data? Problem #2 Expected resolutions Both of these should fail if the data does not match. #2: Bring up new sets with existing data. |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 13/Jun/11 ] |
|
I've made a new ticket for the initiate() vs. add() behavior discrepancy. |
| Comment by Kristina Chodorow (Inactive) [ 27/May/11 ] |
|
I don't think Problem #2 is fixable, the basic premise of fastsync is that you have a known good set of data that the DB doesn't have to check. If you don't, then you have to resync. |