-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.3
-
Component/s: None
-
None
-
(copied to CRM)
-
Empty show more show less
Looks like `startSession` fails randomly with `Current topology does not support sessions` even when sessions are supported (connected to Atlas).
I've encountered this error only twice and It seems to happen in cases when the connection is in some specific state (maybe idle for some time, or the server was doing something?). Retrying immediately after worked.
It would be nice to be able to rely on `startSession` to be working consistently if possible: except for this issue startSession / killSessions seems to be a viable way to cancel background operations in any mongo > 4 (ie. implement `ctrl+c` in mongosh and cancellation buttons in Compass).