[SERVER-47714] Secondary asserts on system.profile collection with WiredTigerRecordStore::insertRecord 95: Operation not supported Created: 23/Apr/20 Updated: 29/Oct/23 Resolved: 15/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog |
| Affects Version/s: | 4.2.8 |
| Fix Version/s: | 4.2.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dmitry Ryabtsev | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: | 1. Create two member replica set
3. On the member with _id: 0 add this to the configuration file:
4. Stop and re-start the _id: 0 member
6. Check if the system.profile collection was created:
7. Check if you see messages similar to the following in the mongod log
|
||||||||||||||||||||
| Sprint: | Execution Team 2020-06-15, Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||||||
| Description |
|
I've managed to reproduce this behaviour on v4.2.1 and 4.2.6 (latest). If a replica set member is started with the database profiler enabled in the configuration it will keep asserting failing to create system.profile collection. Turning profiling on and off makes the errors cease:
|
| Comments |
| Comment by Dejun Xia [ 16/Jul/20 ] |
|
@Eric Milkie Thanks for for the work, we will upgrade to the new version soon. |
| Comment by Githook User [ 15/Jul/20 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}Message: |
| Comment by Githook User [ 15/Jul/20 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}Message: |
| Comment by Eric Milkie [ 14/Jul/20 ] |
|
I can reproduce the issue and am now working on a fix. |
| Comment by Dejun Xia [ 10/Jul/20 ] |
|
Hello, everyone, I wonder when this issue will be fixed in 4.2 bugfix version, we have encountered many times of this problem in Alibaba MongoDB Service.Looking forward to your reply, thanks. |
| Comment by Cen Zheng [ 21/May/20 ] |
|
Hi, We found not only secondary nodes will encounter this issue, primary node will also. I have uploaded both mongod.log and related FTDC file. Please help investigate this issue. Thanks! |