abort operations with AbortController

[jimmywarting]

An AbortController can come from multiple places such as a spec compatible whatwg/Request or some server that wraps incoming http server request into a standard whatwg/request with a AbortSignal. they can also be constructed with new AbortController() or the new proposed AbortController.timeout(ms)

This are useful b/c the can cancel multiple operations simultaneously at once.
calling abort() on the controller could close the request connection, stop listening on a other multiple event listener, addEventListener(name, fn, { signal }) and many more thing at once. this signal could also be forwarded to mongoose operation too, to abort any mongodb operation if say a user decide to close the request/connection

it would be cool if the .find(), and .cursor() could take an optional { signal } parameter that abort the hole operation when the signal dispatch an abort event, likewise with db.connect() and also aggregation

[Uzlopak]

Makes sense. Does mongodb native driver support an AbortController?

[jimmywarting]

Hmm, don't know. don't think so...?

[vkarpov15]

The MongoDB Node driver doesn't currently support an AbortController. In theory, this could be possible with killOp().

[accidentalprogrammer]

Any latest info on this? I would also really like to have this feature.

[vkarpov15]

We added support for aborting an eachAsync() with AbortController here: #12323 . What operations do you want to be able to cancel @accidentalprogrammer ?

[accidentalprogrammer]

@vkarpov15 thanks for that info I'll go through that PR and see if it helps me but just I'll explain my problem just in case I'm looking at it the wrong way.
So we have some long running queries in our system which take a lot of time to return and sometimes user gives a very big time range and moves away from the page even before the result returns but that mongo query keeps executing and hogs the connection pool and sometimes we run out of connections and the the UI is unable to load any data after that until some connection frees up or we restart the mongoose server.
What I was looking into is if I can somehow cancel the mongo query that has been run in the event that the underlying http request is cancelled and that data is no longer needed.

[vkarpov15]

There are a few problems with that approach, most notably because there isn't really a good way to tell whether the underlying HTTP request has been cancelled or not. I'd recommend just using maxTimeMS: https://thecodebarbarian.com/slow-trains-in-mongodb-and-nodejs