Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
2.4.3
-
None
-
ALL
-
-
(copied to CRM)
-
0
Description
Open multiple tailable cursors with or without awaitdata against a capped collection causes sustained high cpu (on my machine about 30% cpu). A single cursor is about 5% cpu.
Confirmed using the node.js driver and java driver.
Attachments
Issue Links
- depends on
-
SERVER-6405 Wrapper for NamespaceDetails and NamespaceDetailsTransient
-
- Closed
-
- duplicates
-
SERVER-18184 Add awaitData support to getMore command
-
- Closed
-
- is duplicated by
-
SERVER-10226 Excessive CPU usage for idle tailable cursors
-
- Closed
-
- related to
-
SERVER-14802 improve sleepmillis() resolution under Windows
-
- Closed
-
- links to
(3 links to)