[THRIFT-5502] Is it necessary to report CONNECTION RESET as an ERROR?

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 0.14.0, 0.14.1
• Fix Version/s: 0.17.0
• Component/s: Java - Library
• Assignee: Sylwester Lachiewicz
• Reporter: Tian Jiang
• Created: 21/Jan/22 10:31
• Updated: 24/Feb/23 01:45
• Resolved: 25/Aug/22 20:26

Description

I notice that in your Java implementation if a connection throws an exception, you will log it or not depending on the type of the exception. Currently, only two kinds of exceptions will be ignored: TIME_OUT and EOF.

However, a common case is when a client exits without closing the connection properly, the server will receive CONNECTION RESET instead of EOF. It is very likely that human users will close client programs directly rather than use some "exit" command.

I understand that it is arguable whether an abnormally-exit client should be reported. But in my opinion, it should at least not generate an ERROR log, as ERROR logs are very sensitive in production systems and may trigger further alerts, while an abnormally-exit client is not actually some error that should be handled by the server maintainers.

Issue Links

• is related to: IOTDB-2467 [THRIFT/CLI]Unnecessary error messages are reported？
• links to: GitHub Pull Request #2608