You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Rajeshbabu Chintaguntla (JIRA)" <ji...@apache.org> on 2015/09/01 08:04:45 UTC
[jira] [Commented] (PHOENIX-2179) Trace output contains extremely
large number of readBlock rows
[ https://issues.apache.org/jira/browse/PHOENIX-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724846#comment-14724846 ]
Rajeshbabu Chintaguntla commented on PHOENIX-2179:
--------------------------------------------------
Since it's in HBase to disable it we need code change in HBase.
> Trace output contains extremely large number of readBlock rows
> --------------------------------------------------------------
>
> Key: PHOENIX-2179
> URL: https://issues.apache.org/jira/browse/PHOENIX-2179
> Project: Phoenix
> Issue Type: Bug
> Reporter: Mujtaba Chohan
> Priority: Minor
> Labels: Tracing
>
> As an example, trace over a 10M row table using count * query produces over 250K rows for HFileReaderV2.readBlock.
> {code}
> select count(*), description from SYSTEM.TRACING_STATS WHERE TRACE_ID=X group by description;
> +------------------------------------------+------------------------------------------+
> | COUNT(1) | DESCRIPTION |
> +------------------------------------------+------------------------------------------+
> | 3 | ClientService.Scan |
> | 253879 | HFileReaderV2.readBlock |
> | 1 | Scanner opened on server |
> +------------------------------------------+------------------------------------------+
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)