[
https://issues.apache.org/jira/browse/IMPALA-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165091#comment-17165091
]
ASF subversion and git services commented on IMPALA-9987:
---------------------------------------------------------
Commit ee18dc383ed7f62630c9e770d14f5851a8747b81 in impala's branch
refs/heads/master from Thomas Tauber-Marshall
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=ee18dc3 ]
IMPALA-9987: Improve logging around HTTP connections
- Previously, every new connection resulted in three log messages at
VLOG(1) in TAcceptQueueServer: indicating a new connection being
made, the start of connection setup, and the end of connection
setup. This patch moves the second two messages to VLOG(2).
- The webserver no longer logs an error if LDAP auth in enabled and a
client tries to connect without providing an auth header, as this
case is generally not actually an error and logging it as such can
be confusing.
- VLOG(4) is added to print HTTP headers received by both the Thrift
HTTP server and the webserver for debugging.
Testing:
- Manually enabled different logging levels and checked for expected
logs.
Change-Id: I38a32b8746084ea44b098a6ccce4ce01947ae88f
Reviewed-on: http://gerrit.cloudera.org:8080/16230
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Improve logging around HTTP connections
> ---------------------------------------
>
> Key: IMPALA-9987
> URL: https://issues.apache.org/jira/browse/IMPALA-9987
> Project: IMPALA
> Issue Type: Task
> Components: Backend
> Affects Versions: Impala 4.0
> Reporter: Thomas Tauber-Marshall
> Assignee: Thomas Tauber-Marshall
> Priority: Major
> Fix For: Impala 4.0
>
>
> The existing logging around HTTP connections is poor. Some improvements that
> could be made:
> - There are several messages that are logged on every connection creation and
> disconnect, sometimes resulting in large amounts of un-informative log spam.
> These could be moved to a higher vlog level.
> - More vlog-ing in general could be added to help in debugging issues.
> - The frequent "auth failed" message that gets logged in the
> not-actually-an-error situation that a client doesn't send an auth header on
> its first connection attempt until it sees the WWW-Authenticate can be
> misleading.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
