>From your screenshot, that's my interpretation, but I'm not that
familiar with the zipkin interface, or spark-shell.
However, it is possible that tserver is doing some sub-task that isn't
traced, or whose trace isn't properly closed and sent to the span
receiver that could explain the time. It's
Added SpanReceiver for Zipkin and now trace entries make more sense.
Thanks,
On Fri, Feb 28, 2020 at 10:30 PM Christopher wrote:
> 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
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
