Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories Atlas
Created by Guest
Created on Jan 25, 2021

ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps

In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances. As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it. Please provide a way to simply ignore the notimeout option, instead of breaking its connection. Thanks!
  • Attach files
  • Guest
    Jan 27, 2021
    Thank you for the feedback Jonas. Sent you a direct message for more information on the specific tools you use but feel free to post here as well.