The tracing in Accumulo is instrumented using HTrace. You can
configure any HTrace sink for collecting the trace information. The
built-in one that writes to an Accumulo table (called
"ZooTraceClient") is the default, but you can easily change this by
editing the configuration property for
I've used the Accumulo Tracer API before to help identify bottlenecks in my
scans. You can find the most recent traces in the Accumulo Monitor UI, and
there are also some tools you can use to view the contents of the trace
table. See section 18.10.4 "Viewing Collected Traces" at
Hi,
Our Accumulo deployment uses custom Authenticator and Authorizer and also
attaches few custom filters/iterators to tables during scan time. The
challenge is that we are seeing very slow response when loading the table
inside a spark shell and doing a simple count.
I was thinking of adding
