Takuya Kojima commented on DRILL-4876:
Thank you for your comment and attachment.
I understand your point. If the connection is failed, I must reconnect with new
As you said, "would be a great enhancement" but, "it's not supported today."
So, what should I do at this time for this issue ticket? (resolve / close
/reopen new ticket and so on.)
I'm not sure the policy of that, so any recommendation might be helpful for me.
> 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.6.0, 1.7.0, 1.8.0
> Environment: CentOS 7
> Reporter: Takuya Kojima
> Assignee: Sorabh Hamirwasia
> Priority: Minor
> Attachments: 1_normal.png, 2_after_restart.png,
> 5_after_disconnected.png, DrillClientConnectionResetTest.java,
> 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