Sergey Shelukhin created THRIFT-4182:
----------------------------------------
Summary: separate loggers for client and server errors
Key: THRIFT-4182
URL: https://issues.apache.org/jira/browse/THRIFT-4182
Project: Thrift
Issue Type: Improvement
Reporter: Sergey Shelukhin
As it stands, a malicious (or broken) client can flood the logs with
callstacks, e.g. {noformat}
2017-04-13 11:26:57,913 ERROR HiveServer2-Handler-Pool: Thread-96:
server.TThreadPoolServer (TThreadPoolServer.java:run(297)) - Error occurred
during processing of message.
java.lang.RuntimeException:
org.apache.thrift.transport.TSaslTransportException: No data or no sasl data in
the stream
at
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
[snip]
Caused by: org.apache.thrift.transport.TSaslTransportException: No data or no
sasl data in the stream
at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:328)
at
org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
at
org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
... 10 more
{noformat}
Perhaps a class of exceptions should be introduced for client errors, then a
separate catch block and a logger can be added so that these errors could be
suppressed without suppressing all the logging for the class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
