drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Takuya Kojima (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-4876) Remain disconnected connection
Date Sun, 04 Sep 2016 14:05:21 GMT
Takuya Kojima created DRILL-4876:
------------------------------------

             Summary: Remain disconnected connection
                 Key: DRILL-4876
                 URL: https://issues.apache.org/jira/browse/DRILL-4876
             Project: Apache Drill
          Issue Type: Bug
          Components: Client - JDBC
    Affects Versions: 1.8.0, 1.7.0, 1.6.0
         Environment: CentOS 7
            Reporter: Takuya Kojima
            Priority: Minor


I'm using drill via Java Application on Tomcat with JDBC driver.

I found that disconnected connection is not released when restart a drillbit.
Drillbit is restarted, but JDBC's connection keeps to try to connect the connection which
started before restart.

Expected behavior is its connection release and reconnect when drillbit is restarted, but
as a matter of fact, the connection will be released after elapsed time of "minEvictableIdleTimeMillis"
setting.

As a result, the application can't connect in the meantime despite drillbit is active.

I thought this is not major issue, but Postgres and Vertica's JDBC driver works well in the
same situation. I spend the much time to identify the cause, so I create a new issue of this.

The attached is log and JMX's monitor graph with 1.6.0's JDBC driver, but I also get it with
1.7.0 and 1.8.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message