The mongo log in production shows tons of reconnections for these queries. It also shows a large spike in CPU usage after about 10 minutes of inactivity.
This should fix that problem, and keep the tailable cursor open, as expected.
Coverage remained the same at 83.628% when pulling ad11534ec560af47a402a787a5934f94354e0b25 on bugfix/oplogTimeout into 552cdc7eb6aa53eee3a473e84a44a7196ea55b30 on develop.
The mongo log in production shows tons of reconnections for these queries. It also shows a large spike in CPU usage after about 10 minutes of inactivity.
This should fix that problem, and keep the tailable cursor open, as expected.
This change is