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.