[jira] [Commented] (HIVE-23237) Display HiveServer2 hostname in the operation logs

["Zhihua Deng (Jira)" <ji...@apache.org>]

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

Zhihua Deng commented on HIVE-23237:
------------------------------------

This may resolved at https://issues.apache.org/jira/browse/HIVE-23722

> Display HiveServer2 hostname in the operation logs
> --------------------------------------------------
>
>                 Key: HIVE-23237
>                 URL: https://issues.apache.org/jira/browse/HIVE-23237
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Miklos Szurap
>            Priority: Major
>              Labels: supportability
>
> Hive deployments often have an external load-balancer in front of multiple HiveServer2 instances. 
> In such cases the client does not know which HiveServer2 it is connected to. If there are some issues all HiveServer2 logs have to be searched for clues instead of directly going to the right host. It would be great if the HS2 hostname was logged to the client logs (for example to beeline's output). 
> We can "work around" by printing out this information with executing a "set hive.server2.thrift.bind.host;" however that requires an explicit modification to every application. 
> Can we print this information in the operation logs and that way streaming it back to the client? 
> Likely some users - customers do not want to expose that, so the behavior should be configurable.
> This could make the issue/error investigation much easier.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)