You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Vihang Karajgaonkar (JIRA)" <ji...@apache.org> on 2018/03/15 17:51:00 UTC

[jira] [Created] (HIVE-18964) HiveServer2 should not log errors when clients issue connection reset

Vihang Karajgaonkar created HIVE-18964:
------------------------------------------

             Summary: HiveServer2 should not log errors when clients issue connection reset
                 Key: HIVE-18964
                 URL: https://issues.apache.org/jira/browse/HIVE-18964
             Project: Hive
          Issue Type: Improvement
          Components: HiveServer2
    Affects Versions: 2.3.2, 3.0.0
            Reporter: Vihang Karajgaonkar
            Assignee: Vihang Karajgaonkar


HiveServer2 logs an ugly exception trace when clients issue a connection reset. There is nothing we can do when the connection is reset. This exception trace should either be ignored or logged only in debug mode.

Things become worse if you are using load balancer like HAProxy which has its own health checks. HAProxy issues a connection reset to "quickly" close the connection once it finds that HS2 is up and available. This spams the logs at a very high frequency and makes them unusable for debugging purposes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)