Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/255
> The multithreaded nature of mutations are now too unpredictable and time
sensitive to reliably look for "sendMutations" traces here.
Do you have more specifics as to why this is?
ACCUMULO-1755 added that single-thread that will bin and then send
mutations. It seems odd that we would lose the sendMutations span (as that code
hasn't really changed, just how it gets invoked).
Do you have the actual trace hierarchy handy from a test failure? Maybe it
would ring a bell for @billierinaldi. I recall debugging weird tracing with her
in a starbucks once upon a time.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
