[
https://issues.apache.org/jira/browse/PHOENIX-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122465#comment-15122465
]
Jan Fernando commented on PHOENIX-2640:
---------------------------------------
Absolutely agree the Phoenix community should not be building UIs and advanced
tooling at this time! What I do think would be useful is to have a way to kill
a query from a client running on a different JVM. The use case is where we have
many stateless app servers all running Phoenix and a central administration
console. If PhoenixRuntime could expose all currently running statements it
would allow people to build tooling on top of a REST API, for example, to view
and kill queries from a central administration console. I see this as small
additional layer on top of Statement.cancel(). My 2 cents :)
> Make it possible to kill running queries (and ideally list them too)
> --------------------------------------------------------------------
>
> Key: PHOENIX-2640
> URL: https://issues.apache.org/jira/browse/PHOENIX-2640
> Project: Phoenix
> Issue Type: New Feature
> Reporter: John Wilkinson
>
> It would be useful to be able to find and kill queries that have gone on
> for a long time.
> Right now, it looks like there is no way other than killing the client, and no
> way to find running queries other than to have the client track them.
> One useful step would be to implement Statement.cancel(), which would allow
> client code to cleanly kill queries.
> Even better from a dev-ops/support point of view would be the ability to see
> running queries via a UI or API of some sort and kill them from there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
