[SERVER-15516] 2.6.x secondaries cannot apply update performed by 2.4.x primary, fassert Created: 02/Oct/14 Updated: 10/Dec/14 Resolved: 08/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Eric Milkie |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Update on the primary of mixed set as follows: |
||||||||
| Participants: | |||||||||
| Description |
|
If 2.4.x primary accepts an update which sets a field named "" (see related SERVER-6852) when 2.6.x tries to replicate it, it gets an fassert since 2.6.x primary would not allow such an update.
|