hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12949) Add HTrace to the s3a connector
Date Sun, 19 Jun 2016 20:29:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338785#comment-15338785
] 

Steve Loughran commented on HADOOP-12949:
-----------------------------------------

+ we'll want to have the htrace context ID go all the way down to s3 by way of the HADOOP-13122
UA header. That lets your storage infra provider know which queries are causing problems,
and, if this goes via a proxy capable of reading the HTTP Requests, lets them sample and correlate
with network load

> Add HTrace to the s3a connector
> -------------------------------
>
>                 Key: HADOOP-12949
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12949
>             Project: Hadoop Common
>          Issue Type: Improvement
>          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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message