[SERVER-31823] Turning on the profiler inhibits initiating a replica set Created: 03/Nov/17 Updated: 30/Oct/23 Resolved: 07/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.6.0-rc2 |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | 1. Start mongod 2. Start mongo This will result in a failure of the command with: |
||||
| Sprint: | Storage 2017-11-13 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Turning on the profiler on a replicated database writes a new system.profile collection to the database, even if initiate has not yet run. Subsequently, if you then run initiate, it will fail because it will attempt to assign a UUID to the system.profile collection, but this is prohibited because the node is not yet a PRIMARY. |
| Comments |
| Comment by Githook User [ 07/Nov/17 ] |
|
Author: {'name': 'Eric Milkie', 'username': 'milkie', 'email': 'milkie@10gen.com'}Message: |
| Comment by Githook User [ 07/Nov/17 ] |
|
Author: {'name': 'Eric Milkie', 'username': 'milkie', 'email': 'milkie@10gen.com'}Message: |
| Comment by Eric Milkie [ 03/Nov/17 ] |
|
A corollary to this is that if you attempt this repro and then restart mongod, it thinks you have data already, and thus fails to start up; it suggests you need to run mongodb 3.4! |