[SERVER-17129] logOp fassert when creating namespace on stepped-down primary via legacy update Created: 30/Jan/15 Updated: 18/Sep/15 Resolved: 30/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.0-rc7 |
| Fix Version/s: | 3.0.0-rc8 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Kamran K. | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
This bug only seems to apply to non-write command mode. It does not seem to affect 2.6.7.
Version: 94cb08d1d1a147 |
| Comments |
| Comment by Githook User [ 02/Feb/15 ] | ||||
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: (cherry picked from commit 8e11987b6f7f393bbf1c468f7626d2a4993ae0cb) | ||||
| Comment by Githook User [ 30/Jan/15 ] | ||||
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: | ||||
| Comment by Eric Milkie [ 30/Jan/15 ] | ||||
|
I've proposed a code fix. In testing with a 2.4 shell, I get the expected result:
In a 2.8 shell in legacy-write mode, it seems to swallow the exception and just shows that it didn't do any upserts:
I'm not sure if this behavior is intentional, but at least it's the same as 2.6. | ||||
| Comment by Eric Milkie [ 30/Jan/15 ] | ||||
|
I suspect the bug is as simple as attempting to send a legacy upsert to a secondary for a namespace that doesn't yet exist. |