-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add admin API to kill running queries #290
Comments
So there isn't exactly an easy way to stop queries but we can put in a safe guard that will only let the current running query finish and then cancel all others after. That should work for now. Otherwise we'd have to shut down the ForkJoinPool and then restore it somehow - seems too catastrophic for the application. |
Just some confirmation on how this works. There is now a You can always check If you are in guard mode, then no other queries except the one that is currently running (prior to entering guard mode) will run. Anything queue'd up will fail instantly with an Exception saying If you are not in guard mode then all queries will continue to process in NNA as usual. Guard mode does not stop the SuggestionsEngine - it will continue to process in the background as usual. |
Seen instances where an NNA instance can get locked up from running expensive queries. Would be nice to interrupt the requests and get back to stable state.
This issue is to try to make that possible.
The text was updated successfully, but these errors were encountered: