[
https://issues.apache.org/jira/browse/PHOENIX-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289497#comment-17289497
]
chaoWang commented on PHOENIX-6050:
-----------------------------------
oh，thanks big brother ，I know your meaning，or we could provide one new
parameter？which control scan parallel thead pool .
---Original---
From: "Istvan Toth (Jira)"<j...@apache.org>
Date: Wed, Jan 6, 2021 20:21 PM
To: "576749262"<576749...@qq.com>;
Subject: [jira] [Commented] (PHOENIX-6050) Set properties is invalid
[
https://issues.apache.org/jira/browse/PHOENIX-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259664#comment-17259664
]
Istvan Toth commented on PHOENIX-6050:
--------------------------------------
This has nothing to with using Query Server or not.
If your Phoenix thick client is configured correctly, it has access to the
cluster's hbase-site.xml, and will pick up the parameter from there.
If you are not doing this already, you need to copy the cluster's
hbase-site.xml to your client, and it to the classpath.
> Set properties is invalid
> -------------------------
>
>
Key: PHOENIX-6050
>
URL: https://issues.apache.org/jira/browse/PHOENIX-6050
>
Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 4.13.1, 5.0.0
> Environment: phoenix 4.13.1
> hbase 1.3.1
>
Reporter: Chao Wang
>
Assignee: Chao Wang
>
Priority: Major
>
Fix For: 5.1.0
>
> Attachments:
PHOENIX-6050.master.001.patch, PHOENIX-6050.master.002.patch
>
>
> I set properties in client, which are "phoenix.query.threadPoolSize", but
this is invalid. ThreadPool always use default value (128).
> code is:
> Properties properties = new Properties();
> properties.setProperty("phoenix.query.threadPoolSize","300");
> PropertiesResolve phoenixpr = new PropertiesResolve();
> String phoenixdriver =
phoenixpr.readMapByKey("com/main/SyncData.properties", "phoenix_driver");
> String phoenixjdbc =
phoenixpr.readMapByKey("com/main/SyncData.properties", "phoenix_jdbc");
> Class.forName(phoenixdriver);
> return DriverManager.getConnection(phoenixjdbc,properties);
> throw is:
> Error: Task
org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@6e91893 rejected
from org.apache.phoenix.job.JobManager$1@26ae880a[Running, pool size = 128,
active threads = 128, queued tasks = 5000, completed tasks = 36647]
(state=08000,code=101)
> org.apache.phoenix.exception.PhoenixIOException: Task
org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@6e91893 rejected
from org.apache.phoenix.job.JobManager$1@26ae880a[Running, pool size = 128,
active threads = 128, queued tasks = 5000, completed tasks = 36647]
> at
org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:120)
> at
org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:1024)
> at
org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:916)
> ^Reason:^
> I find PhoenixDriver create threadpool before init config from properties.
when create threadpool , config is always default value .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
> Set properties is invalid
> -------------------------
>
> Key: PHOENIX-6050
> URL: https://issues.apache.org/jira/browse/PHOENIX-6050
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 4.13.1, 5.0.0
> Environment: phoenix 4.13.1
> hbase 1.3.1
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Fix For: 5.1.0
>
> Attachments: PHOENIX-6050.master.001.patch,
> PHOENIX-6050.master.002.patch
>
>
> I set properties in client, which are "phoenix.query.threadPoolSize", but
> this is invalid. ThreadPool always use default value (128).
> code is:
> Properties properties = new Properties();
> properties.setProperty("phoenix.query.threadPoolSize","300");
> PropertiesResolve phoenixpr = new PropertiesResolve();
> String phoenixdriver =
> phoenixpr.readMapByKey("com/main/SyncData.properties", "phoenix_driver");
> String phoenixjdbc = phoenixpr.readMapByKey("com/main/SyncData.properties",
> "phoenix_jdbc");
> Class.forName(phoenixdriver);
> return DriverManager.getConnection(phoenixjdbc,properties);
> throw is:
> Error: Task
> org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@6e91893 rejected
> from org.apache.phoenix.job.JobManager$1@26ae880a[Running, pool size = 128,
> active threads = 128, queued tasks = 5000, completed tasks = 36647]
> (state=08000,code=101)
> org.apache.phoenix.exception.PhoenixIOException: Task
> org.apache.phoenix.job.JobManager$InstrumentedJobFutureTask@6e91893 rejected
> from org.apache.phoenix.job.JobManager$1@26ae880a[Running, pool size = 128,
> active threads = 128, queued tasks = 5000, completed tasks = 36647]
> at
> org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:120)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:1024)
> at
> org.apache.phoenix.iterate.BaseResultIterators.getIterators(BaseResultIterators.java:916)
> ^Reason:^
> I find PhoenixDriver create threadpool before init config from properties.
> when create threadpool , config is always default value .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
