This is most likely a bug. I think it's similar to the following bug: https://issues.apache.org/jira/browse/DRILL-3763
Please take a look at it and feel free to add more information to the ticket. Thanks On Tue, Sep 29, 2015 at 2:20 AM, xia <sissyxbx...@163.com> wrote: > Hi, everyone, > > > I'm new to drill. > > > I am running concurrent queries each holds its own JDBC connection to > single drillbit node. > > > As I found, if one of the connections is closed, it will affect other > connections and lead to unexpected channel close exception. > > > So does drill jdbc support connection pool? > > > How am I supposed to manage concurrent connections without interfering > with each other? > > > Many thanks! > > > Iris -- Abdelhakim Deneche Software Engineer <http://www.mapr.com/> Now Available - Free Hadoop On-Demand Training <http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available>
