[
https://issues.apache.org/jira/browse/PHOENIX-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244788#comment-14244788
]
Andrew Purtell commented on PHOENIX-1519:
-----------------------------------------
bq. Or is it more of something that would be used in a perf testing environment
where we'd need to information generated to be only for a particular query (in
which case the above JIRAs are more important)?
Being HTrace based, with HTrace support down through HBase and HDFS, this is
what I think I'd use it for... getting a full stack view when investigating
performance issues with total system or individual queries.
> Determine the usefulness of tracing
> -----------------------------------
>
> Key: PHOENIX-1519
> URL: https://issues.apache.org/jira/browse/PHOENIX-1519
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
>
> In order to help prioritize the child JIRAs under PHOENIX-1121, we need to do
> a usability study around tracing. What problem(s) are we trying to solve and
> what's the delta between the existing tracing feature and the required
> tracing features. Are we capturing enough information to be useful? Is it
> structured in a such a way to lend itself to analysis?
> For example, is the main use case of tracing to determine the top 10 queries
> that take the longest amount of time in production? Would we then want
> tracing on all the time, so having a way to enable/disable tracing
> (PHOENIX-1433, PHOENIX-1191, PHOENIX-1518, PHOENIX-1115) becomes moot.
> Or is it more of something that would be used in a perf testing environment
> where we'd need to information generated to be only for a particular query
> (in which case the above JIRAs are more important)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
