[
https://issues.apache.org/jira/browse/HADOOP-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260508#comment-16260508
]
Steve Loughran commented on HADOOP-12949:
-----------------------------------------
Revisiting this
* yes, it would be good.
* let's not worry about UA headers initially; a later iteration.
* more important: linking across jobs on long lived processes, e.g Spark, Hive
LLAP. We want those tools to create a context, it to propagate over with their
queries, and the store clients to pick that up.
Making a subclass of the S3A phase IV work, targeting Hadoop 3.1.
Patches welcome!
> Add HTrace to the s3a connector
> -------------------------------
>
> Key: HADOOP-12949
> URL: https://issues.apache.org/jira/browse/HADOOP-12949
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Madhawa Gunasekara
> Assignee: Madhawa Gunasekara
>
> Hi All,
> s3, GCS, WASB, and other cloud blob stores are becoming increasingly
> important in Hadoop. But we don't have distributed tracing for these yet. It
> would be interesting to add distributed tracing here. It would enable
> collecting really interesting data like probability distributions of PUT and
> GET requests to s3 and their impact on MR jobs, etc.
> I would like to implement this feature, Please shed some light on this
> Thanks,
> Madhawa
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
