[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.
When i checked the mongodb log, i saw two different types of behavior/errors at different times:

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:
warning: slow scan in allocFromFreeList (in write lock)
Sun Dec 10 13:00:07.698 [conn10363640] warning: newExtent 2223 scanned
insert xxxx ninserted:1 keyUpdates:0 locks(micros) w:10384820 10384ms

These two situations are causing an outage and should be fixed asap.

We are currently using 2.4.9 mongodb
I know that mongo upgrade is needed but this version was working fine till recently and nothing changed.
Any pointers will be highly appreciated at your earliest convenience.



 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.
See also our Technical Support page for additional support resources.

Thanks,
Mark

Generated at Thu Feb 08 04:29:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.