[ https://issues.apache.org/jira/browse/ACCUMULO-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746921#comment-13746921 ]
Eric Newton commented on ACCUMULO-1502: --------------------------------------- 1) sure, I think we can update documentation in a branch 2) a new chapter of the user manual would be great 3) yep, but default, only the compactions are traced; you can do a trace from the shell, though. 4) yes 5) the trace should follow the updates, even when they are later pushed out of the batch writer; the trace information should be collected and transferred to the thread pool when the mutations are actually written > 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 > Fix For: 1.6.0 > > > 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