[jira] [Comment Edited] (PHOENIX-6074) Let PQS Act As An Admin Tool Rest Endpoint

["Mehdi Salarkia (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186134#comment-17186134 ] 

Mehdi Salarkia edited comment on PHOENIX-6074 at 8/27/20, 10:38 PM:
--------------------------------------------------------------------

Thanks [~elserj] 
 I have a draft PR that can run the IndexTool inside PQS [https://github.com/apache/phoenix-queryserver/pull/48|https://github.com/apache/phoenix-queryserver/pull/48/files#diff-9880d178245a9b03037412487d69aa72R41]
 However I share the concern of running the IndexTool within the same JVM as PQS could result in performance degradation and traffic impact. I'm looking around to find a clean way to solve this issue, one idea could be to run the indexTool via command line which should spin up a new process and won't impact PQS directly. But the implementation can be a complicated and I need to think more about that.

Re:security concern, we can do something like SPENGO to make sure it is available only available to an authorized user.

I will keep working on that change but please take a look and let me know what you think. 


was (Author: m2je):
Thanks [~elserj] 
I have a draft PR that can run the IndexTool inside PQS [https://github.com/apache/phoenix-queryserver/pull/48|https://github.com/apache/phoenix-queryserver/pull/48/files#diff-9880d178245a9b03037412487d69aa72R41]
However I share the concern of running the IndexTool within the same JVM as PQS could result in performance degradation and traffic impact. I'm looking around to find a clean way to solve this issue, one idea could be to run the indexTool via command line which should spin up a new process and won't impact PQS directly. But the implementation can be a complicated I need to think more about that.

Re:security concern for security, we can do something like SPENGO to make sure it is available only available to an authorized user.

I will keep working on that change but please take a look and let me know what you think. 

> Let PQS Act As An Admin Tool Rest Endpoint
> ------------------------------------------
>
>                 Key: PHOENIX-6074
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6074
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: queryserver
>            Reporter: Mehdi Salarkia
>            Assignee: Mehdi Salarkia
>            Priority: Minor
>
> In our production environment we need to create a lot of indexes and use indexTool to build the index also sometime use tools like indexScrutiny to verify the health and status of indexes, etc.
> PQS can act as a REST API end point (proxy) that allows developers to call and run commands that phoenix currently support via command line only:
>  * IndexTool
>  * IndexScrutiny
> Benefits:
>  # Allow developers to develop tools in their application to run and integrate phoenix command line tools into their application without a human intervention.
>  # Remove unnecessary access permission to production from non admins.
>  # Simplify the Index management (or any other future command line tool that will be added to phoenix) and remove the possibility of human error, etc.
> I was looking at the implementation PHOENIX-5827 as an example. I think we can simply define a new context and use that to trigger phoenix command line tools from PQS and return the result (perhaps the MR job link,...) to the client.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)