[
https://issues.apache.org/jira/browse/PHOENIX-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7523:
---------------------------------
Description:
We can tune the thick client JVM settings via PHOENIX_OPTS, and with the
changes in PHOENIX-7520 HBASE_OPTS is also applied.
However, there is no similar mechanism for PQS.
The plan:
- Parse and apply hbase-env.*, just like Phoenix does
- Fall back to $HBASE_OPTS if PHOENIX_QUERYSERVER_OPTS is not set starting
PQS
was:
We can tune the thick client JVM settings via PHOENIX_OPTS, and with the
changes in PHOENIX-7520 HBASE_OPTS is also applied.
However, there is no similar mechanism for PQS.
The plan:
- Parse and apply hbase-env.*, just like Phoenix does
- Define new env. variables PHOENIX_QUERYSERVER_OPTS and
PHOENIX_SQLLINE_THIN_OPTS
- Apply $HBASE_OPTS and and PHOENIX_QUERYSERVER_OPTS when starting PQS.
- Apply $PHOENIX_SQLLINE_THIN_OPTS when starting sqlline-thin.
> Parse hbase-env.sh in PQS scripts, and and fall back to HBASE_OPTS in
> queryserver.py
> ------------------------------------------------------------------------------------
>
> Key: PHOENIX-7523
> URL: https://issues.apache.org/jira/browse/PHOENIX-7523
> Project: Phoenix
> Issue Type: Improvement
> Components: queryserver
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> We can tune the thick client JVM settings via PHOENIX_OPTS, and with the
> changes in PHOENIX-7520 HBASE_OPTS is also applied.
> However, there is no similar mechanism for PQS.
> The plan:
> - Parse and apply hbase-env.*, just like Phoenix does
> - Fall back to $HBASE_OPTS if PHOENIX_QUERYSERVER_OPTS is not set
> starting PQS
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
