[SERVER-18962] Fatal assertion on profiling-enabled secondary when dropping system.profile collection on primary Created: 12/Jun/15 Updated: 31/Aug/16 Resolved: 17/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.1.3 |
| Fix Version/s: | 3.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | 32qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||
| Sprint: | RPL 5 06/26/16 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
If profiling is enabled on a secondary and a system.profile drop occurs on the primary, the secondary will abort, as of 3.1.2. In previous versions, including 3.0.4-rc0, the same set of operations would result in a warning and a failed drop. 3.1.2+
3.1.1 and 3.0.4-rc0
|
| Comments |
| Comment by Githook User [ 17/Jun/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Githook User [ 17/Jun/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 17/Jun/15 ] |
|
Matt, please take a look at |
| Comment by Scott Hernandez (Inactive) [ 16/Jun/15 ] |
|
We should also ignore replicated operations on that collection for upgrade compatibility. |
| Comment by Eric Milkie [ 16/Jun/15 ] |
|
Dropping system.profile should not replicate, since the items in that collection are not replicated. |
| Comment by Kamran K. [ 15/Jun/15 ] |
|
The warning -> fassert change was introduced by |