You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "jaanai (JIRA)" <ji...@apache.org> on 2019/02/28 02:12:00 UTC
[jira] [Updated] (PHOENIX-5169) Query logger is still initialized
for each query when the log level is off
[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jaanai updated PHOENIX-5169:
----------------------------
Description:
we will still invoke createQueryLogger in PhoenixStatement for each query when query logger level is OFF, which has significant throughput impacts under multiple threads.
The below is jstack with the concurrent query:
!https://gw.alicdn.com/tfscom/TB1HC3bI4TpK1RjSZFMXXbG_VXa.png|width=500,height=400!
was:
we will still invoke createQueryLogger in PhoenixStatement for each query when query logger level is OFF, which has significant throughput impacts under multiple threads.
The below is jstack with the concurrent query:
!https://gw.alicdn.com/tfscom/TB1HC3bI4TpK1RjSZFMXXbG_VXa.png|width=500,height=400!
> Query logger is still initialized for each query when the log level is off
> --------------------------------------------------------------------------
>
> Key: PHOENIX-5169
> URL: https://issues.apache.org/jira/browse/PHOENIX-5169
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: jaanai
> Assignee: jaanai
> Priority: Major
> Attachments: image-2019-02-28-10-05-00-518.png
>
>
> we will still invoke createQueryLogger in PhoenixStatement for each query when query logger level is OFF, which has significant throughput impacts under multiple threads.
> The below is jstack with the concurrent query:
> !https://gw.alicdn.com/tfscom/TB1HC3bI4TpK1RjSZFMXXbG_VXa.png|width=500,height=400!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)