[SERVER-16932] Don't let 2.6 replset member initial sync from 2.8 member running wiredTiger Created: 20/Jan/15 Updated: 28/Jan/15 Resolved: 28/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
It's currently legal to do an initial sync from a 2.6 node to a 2.8 node running with wiredTiger. The secondary gives no warning that no data has been synced, despite not being able to find any indexes or collection data. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 20/Jan/15 ] |
|
Alternatively, we could fix the driver itself... Might be easier in the end. Apparently this idea has been floated by scotthernandez/tyler.brock@gmail.com |