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

Jared Winick commented on ACCUMULO-1502:
----------------------------------------

Here is my info. Thanks for getting this merged, hopefully I can continue to 
contribute to some of the other tracing features.

username: jaredwinick
name: Jared Winick
organization: <a href="http://www.koverse.com";>Koverse</a>
timezone: MT (-7 / -6)

Thanks again!
                
> Add Trace Table docs to user manual
> -----------------------------------
>
>                 Key: ACCUMULO-1502
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1502
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: docs, trace
>            Reporter: Sean Busbey
>            Assignee: Jared Winick
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-1502.patch
>
>
> Our feature list includes:
> {quote}
> TRACING
> It can be difficult to determine why some operations are taking longer than 
> expected. For example, you may be looking up items with very low latency, but 
> sometimes the lookups take much longer. Determining the cause of the delay is 
> difficult because the system is distributed, and the typical lookup is fast. 
> Accumulo has been instrumented to record the time that various operations 
> take when tracing is turned on. The fact that tracing is enabled follows all 
> the requests made on behalf of the user throughout the distributed 
> infrastructure of Accumulo, and across all threads of execution.
> {quote}
> and the user manual makes no mention of the facility, its defaults, how to 
> configure it, nor how to leverage it in ops.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to