[SERVER-11881] addUser crashing 2.4 mongod in mixed version replica set Created: 27/Nov/13 Updated: 10/Dec/14 Resolved: 14/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Stability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adinoyi Omuya | Assignee: | Andy Schwerin |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Not sure if this is expected behavior but to reproduce, start a mixed version replica set with a 2.5.x primary and 2.4 secondar[y/ies]. After initiating the replica set, run the following on the primary.
The 2.4 mongod(s) crash. |
| Comments |
| Comment by Andy Schwerin [ 14/Feb/14 ] |
|
After
Workaround is to restart the node with a 2.6 binary, which we presume to be the user's intention anyhow. |
| Comment by Andy Schwerin [ 03/Dec/13 ] |
|
Similar problem where a 2.4 server can't accept oplog entries that manipulate system.users collections in a 2.6-y way. Because 2.4 does enforcement of system.users schema at a very low level, it's quite difficult to bypass. |
| Comment by Andy Schwerin [ 03/Dec/13 ] |
|
It's not an allowed action. I'm not sure how much work it would be to prevent crashing on the 2.4 instances in this case. |