[SERVER-43369] sudden unexpected Recovery State of mongodb node Created: 18/Sep/19 Updated: 07/Apr/23 Resolved: 19/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pratiksha Aggarwal | Assignee: | Dmitry Agranat |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
On a three member replica set of production environment , mongodb02 server went into sudden recovery state with the high cpu usage of above 90%. In logs we could find that after some slow aggregate queries server transitioned into recovery mode. There was high load on system and our current mongodb version is 3.2 and upgrade to 3.4 will take approx one month. |
| Comments |
| Comment by Dmitry Agranat [ 18/Sep/19 ] |
|
Hi pragupta, MongoDB 3.2 has reached EOL a year ago. If you need further assistance troubleshooting, tuning or upgrading, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. Thank you, |