[SERVER-42493] Replica set crashes Created: 30/Jul/19 Updated: 27/Oct/23 Resolved: 31/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Stability |
| Affects Version/s: | 3.4.16 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Stefan Adamov | Assignee: | Dmitry Agranat |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
Hey guys, we observed the following weird behaviour with the following setup: All times are UTC
You can see attached:
Let me know if you need any more information. |
| Comments |
| Comment by Dmitry Agranat [ 31/Jul/19 ] |
|
Hi adamof, After reviewing the provided data, I was not able to find any bottleneck on the MongoDB side. The fact that after scaling up the servers from 7.4GB RAM to 15GB RAM the issue does not reoccur, indicates that it might have been simply an issue with the amount of memory used by the queries while running. I would also recommend reviewing the queries for tuning as I've noticed the workload sometimes scans ~20 million documents just to return ~700. As I was not able to find an issue on the MongoDB side, I will go ahead and close this ticket. Thank you, |