[SERVER-47179] Requesting 'oplog' serverStatus section crashes mongod when there is no oplog Created: 30/Mar/20 Updated: 29/Oct/23 Resolved: 07/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.3.5 |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Dennis Kuczynski | Assignee: | Lingzhi Deng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Steps To Reproduce: | Our end to end suite is reproducing this regularly. They use a single windows-64-vs2017-compile host.
Our tests are failing since we do not receive the expected monitoring data within our usual timeframe. |
||||||||||||
| Sprint: | Repl 2020-04-20 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We're seeing backtraces during our windows testing of 4.3.5. The tests use a single windows-64-vs2017 host to create standalones, replica sets, and sharded clusters with the latest version of MongoDB 4.3. The crash seems to occur periodically while those items are being monitored by the Cloud Manager MongoDB Agent. Snippet of logs:
|
| Comments |
| Comment by Githook User [ 07/Apr/20 ] | ||||||||||||||
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: (cherry picked from commit d34b92cb31a147cf29fe676081978f3ff7acd79f) | ||||||||||||||
| Comment by Githook User [ 07/Apr/20 ] | ||||||||||||||
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: | ||||||||||||||
| Comment by Lingzhi Deng [ 06/Apr/20 ] | ||||||||||||||
|
I think this was caused by Prior to that commit, this used to return an error:
| ||||||||||||||
| Comment by Eric Milkie [ 04/Apr/20 ] | ||||||||||||||
|
To reproduce this:
2. run serverStatus with oplog section (oplog section is not displayed by default)
This will trigger a crash. |