[
https://issues.apache.org/jira/browse/IMPALA-11850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687157#comment-17687157
]
ASF subversion and git services commented on IMPALA-11850:
----------------------------------------------------------
Commit e17fd9a0d5428306dfa41a041a44c800824d72f6 in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=e17fd9a0d ]
IMPALA-11850 Adds HTTP tracing headers when using the hs2-http protocol.
When using the hs2 protocol with the http transport, include several
tracing http headers by default. These headers are:
* X-Request-Id -- client defined string that identifies the
http request, this string is meaningful only
to the client
* X-Impala-Session-Id -- session id generated by the Impala backend,
will be omitted on http calls that occur
before this id has been generated
* X-Impala-Query-Id -- query id generated by the Impala backend,
will be omitted on http calls that occur
before this id has been generated
The Impala shell includes these headers by default. The command
line argument --no_http_tracing has been added to remove these
headers.
The Impala backend logs out these headers if they are on the http
request. The log messages are written out at log level 2 (RPC).
Testing:
- manual testing (verified using debugging proxy and impala logs)
- new python test
Change-Id: I7857eb5ec03eba32e06ec8d4133480f2e958ad2f
Reviewed-on: http://gerrit.cloudera.org:8080/19428
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> impala-shell: add tracing headers to hs2-http requests
> ------------------------------------------------------
>
> Key: IMPALA-11850
> URL: https://issues.apache.org/jira/browse/IMPALA-11850
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Jason Fehr
> Assignee: Jason Fehr
> Priority: Major
>
> Add 'X-Request-ID' in the http header for hs2-http mode when communicating
> from the impala shell to the impala cluster. This is useful for tracing end
> to end logs when using a reverse proxy such as nginx. Would be good to
> include the X-Request-ID in the server logs also, when it logs rpc requests
> and responses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
