[
https://issues.apache.org/jira/browse/AVRO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Wendell updated AVRO-595:
---------------------------------
Attachment: AVRO-595.patch.v2.txt
Here is a patch update based on the preliminary feedback. I dropped the
querying stuff since it's not yet used. This patch adds the logic behind
aggregating partial spans (which will have been collected from several remote
hosts) and creating traces (extracting RPC call trees from a set of spans).
We talked off-line about redundancy in the data that is collected. We could get
away with only recording a spanID and a parentSpanID for each span, then we can
back-out each trace by following these data (we get to the root of a trace when
we see a null parentSpanID). By adding a traceID unique to each call tree, it
is easier to partition the work of collecting spans into traces as we can
easily group spans by trace before we try back-out a tree (perhaps this is why
Dapper paper describes this method). It also lowers the chance of ID collision
since spanID and parentSpanID are specific to one traceID.
> Add Dapper-Style Tracing Plugin to Avro
> ---------------------------------------
>
> Key: AVRO-595
> URL: https://issues.apache.org/jira/browse/AVRO-595
> Project: Avro
> Issue Type: Sub-task
> Reporter: Patrick Wendell
> Assignee: Patrick Wendell
> Attachments: AVRO-595.patch.v1.txt, AVRO-595.patch.v2.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
