[jira] [Commented] (PHOENIX-1197) Measure the performance impact of enabling tracing

["Pranavan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341551#comment-15341551 ] 

Pranavan commented on PHOENIX-1197:
-----------------------------------

Tracing is actually a specialized form of logging. Logs are primarily consumed by system administrators whereas traces are primarily used by developers. The main intention is to assist developers. 

I found following enhancements to Pheonix would be useful.

Enhancements needed to be added in Apache Phoenix
1.   Trace table is growing in a rapid rate, it should be stopped and only relevant trace data must be stored.
2.   A permission model needed for Apache Phoenix Tracing
3.   It should be agile not like logs
4.   Tracing is done at a lower level, hence the size of trace data will be higher. Currently Trace ON and OFF commands are supported. Anyway, we needs to add more granular level of control because it can seriously affect the performance.


> Measure the performance impact of enabling tracing
> --------------------------------------------------
>
>                 Key: PHOENIX-1197
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1197
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>              Labels: tracing
>
> In Phoenix 4.1, there's a new tracing capability. We should measure the impact of enabling this on a live cluster before turning it on in production.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)