Select Query in runUpdateQuery

We ran a select query in the system.db.runUpdateQuery() on a table of about 300k rows. The thread would not die and the system became very slow after that. We checked and the query remained active hours after the designer where the query had first been run in the script console was closed.

We restarted the server and that took care of the query, which ate up about 25% of our CPU.

Is there a way to kill those threads we see in the gateway status tab so we don’t have to restart the entire server?