You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/07/19 21:33:00 UTC
[jira] [Resolved] (HADOOP-15105) add htrace context to HTTP
requests as ? parameter
[ https://issues.apache.org/jira/browse/HADOOP-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-15105.
-------------------------------------
Resolution: Won't Fix
Wontfix
* HTrace is dead; will be replaced by opentrace at some point
* we can set UA headers on a per-request basis, which will be the way to do it consistently across stores
> add htrace context to HTTP requests as ? parameter
> --------------------------------------------------
>
> Key: HADOOP-15105
> URL: https://issues.apache.org/jira/browse/HADOOP-15105
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Priority: Minor
>
> you can [add x-something query parameters to S3 REST calls|http://docs.aws.amazon.com/AmazonS3/latest/dev/LogFormat.html]
> These then get included in the logs. If the htrace context were passed in this way, you could determine from the S3 logs what query/job an HTTP request ties back to
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org