[
https://issues.apache.org/jira/browse/PHOENIX-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545193#comment-17545193
]
ASF GitHub Bot commented on PHOENIX-6694:
-----------------------------------------
chrajeshbabu commented on PR #80:
URL:
https://github.com/apache/phoenix-connectors/pull/80#issuecomment-1144233048
> +1 to Istvan's suggestion on a unit test, but I can't think of an easy way
to verify that this is effective 🤔
@stoty @joshelser I have tried to add a test case to cover the ptable bytes
parsing and checking in PhoenixTestingDataSource but somehow this not picking
in the tests.
> Avoid unnecessary calls of fetching table meta data to region servers holding
> the system tables in batch oriented jobs in spark or hive otherwise those RS
> become hotspot
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-6694
> URL: https://issues.apache.org/jira/browse/PHOENIX-6694
> Project: Phoenix
> Issue Type: Task
> Components: hive-connector, spark-connector
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Priority: Major
>
> Currently we are preparing the query plan in both data source and partition
> readers which is creating new connection in each worker and job
> initialisation which unnecessarily touch basing all both system catalog
> table, system stats table as well as meta. When there are jobs with millions
> of parallel workers hotspot the region servers holding the meta and system
> catalog as well system stats table. So if we share the same query plan
> between the workers which can avoid the hotspot.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
