7ulyWzh opened a new issue, #16487:
URL: https://github.com/apache/druid/issues/16487
Our project integrates Druid, and the relevant configurations are as follows:
Spring. datasource. druid. time between evaluation run mills=2000
Spring. datasource. ruid. min evitable handle time mills=180000
Spring. datasource. ruid. validation query=SELECT 1
Spring. datasource. ruid. initial size=10
Spring. datasource. ruid. min idle=10
Spring. datasource. ruid. max active=50
Spring. datasource. ruid. keep alive=true
Spring. datasource. ruid. keep alive between time mills=50000
When our project is deployed on machines, the following errors frequently
occur:
"Error druid.sql Statement [Log4jFilter. java: 151] - {conn-15545,
stmt-628970} execute error SELECT 1
Com. mysql. jdbc. exceptions. jdbc4. CommunicationsException: Communications
link failure"
By examining the source code of the Druid, we find that when DestroyTask try
to "keepalive" a connection which has been closed by the database server would
cause this exception. However, this exception is not caught internally by
Druid, and the exception is directly thrown to our application.
Our improvement suggestions are as follows:
When Druid tries to "keepalive" some connections and finds that the
connection still exists in the connection pool, but the database server closes
the connection, Druid should help re-establish the connection instead of
throwing an exception to the application.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
