[SERVER-32312] New collection creation is slow and DB clients see primary as offline Created: 13/Dec/17 Updated: 16/Nov/21 Resolved: 02/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sree Himakunthala | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
We started seeing that the mongodb clients are finding the primary to be down. 1) simple INSERT into a (new non-existing) collection is taking very long time (~16 seconds) at times. The very same insert was running fine for years and nothing else changed 2) I saw the following errors: These two situations are causing an outage and should be fixed asap. We are currently using 2.4.9 mongodb |
| Comments |
| Comment by Mark Agarunov [ 14/Dec/17 ] |
|
Hello sreek95051, Thank you for the report. Unfortunately 2.4.9 is now unsupported, so my recommendation would be to upgrade to the most recent version possible. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Thanks, |