Khurram Faraaz created DRILL-6308:
-------------------------------------
Summary: Exception handling - OOM
Key: DRILL-6308
URL: https://issues.apache.org/jira/browse/DRILL-6308
Project: Apache Drill
Issue Type: Bug
Components: Execution - Flow
Affects Versions: 1.14.0
Reporter: Khurram Faraaz
Assignee: Sorabh Hamirwasia
For RpcHandlers in Drill, when there is an OutOfMemory condition ,then all the
handlers call OutOfMemoryHandler with the caught exception. Every channel,
except for DataServer the default instance of MemoryHandler is used which
throws UnsupportedOperationException. This is misleading since actual exception
is for OutOfMemory not UnsupportedOperationException.
Here is an example where it is not handled the right way.
{noformat}
Caused by: java.lang.UnsupportedOperationException: null
at
org.apache.drill.exec.rpc.OutOfMemoryHandler$1.handle(OutOfMemoryHandler.java:25)
~[drill-rpc-1.13.0-mapr.jar:1.13.0-mapr]
at
org.apache.drill.exec.rpc.SaslEncryptionHandler.encode(SaslEncryptionHandler.java:170)
~[drill-rpc-1.13.0-mapr.jar:1.13.0-mapr]
at
org.apache.drill.exec.rpc.SaslEncryptionHandler.encode(SaslEncryptionHandler.java:44)
~[drill-rpc-1.13.0-mapr.jar:1.13.0-mapr]
at
io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:88)
[netty-codec-4.0.48.Final.jar:4.0.48.Final]
... 25 common frames omitted{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
