You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2020/12/04 03:21:41 UTC
[GitHub] [incubator-dolphinscheduler] BoYiZhang opened a new issue #4161: [Bug][SQL] SQL query mode exception : Failed to obtain JDBC Connection ...
BoYiZhang opened a new issue #4161:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4161
SQL query mode exception : Failed to obtain JDBC Connection ...
The Worker service connects to the database normally, the shell node can query the database normally, and the SQL component "non-query mode" is used normally.
But using "query mode" reports an error.
The exception information is as follows:
This exception also exists in the official druid, and the related issues are as follows:
https://github.com/alibaba/druid/issues/2130
User feedback screenshot:
-------------------------------------------------------------
Worker服务正常连接数据库, shell节点可以正常查询数据库, SQL组件 "非查询模式"正常使用.
但是使用"查询模式"报错.
异常信息如下:
druid 官方也存在这个异常,相关issue如下:
https://github.com/alibaba/druid/issues/2130
---------------------------------------------
用户反馈截图:
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-dolphinscheduler] CalvinKirs closed issue #4161: [Bug][SQL] SQL query mode exception : Failed to obtain JDBC Connection ...
Posted by GitBox <gi...@apache.org>.
CalvinKirs closed issue #4161:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4161
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-dolphinscheduler] CalvinKirs commented on issue #4161: [Bug][SQL] SQL query mode exception : Failed to obtain JDBC Connection ...
Posted by GitBox <gi...@apache.org>.
CalvinKirs commented on issue #4161:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4161#issuecomment-738663082
If the direct connection is possible, but the drive connection is not good, then there may be a drive problem. It is recommended to replace the drive.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-dolphinscheduler] anan0120 commented on issue #4161: [Bug][SQL] SQL query mode exception : Failed to obtain JDBC Connection ...
Posted by GitBox <gi...@apache.org>.
anan0120 commented on issue #4161:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4161#issuecomment-739313659
I have been tossing about the problem for a few days, and I have not been able to locate the specific cause. The driver has also been changed to 5.1.48, the server restarted and other methods have been tried without solution.
It's hard to understand: other operations don't even have any problems with data. Only this sql component sql type is query, and the problem of druid timeout has been reported. I have been thinking about the details of eating, walking, and sleeping that I have overlooked. . . I finally decided on the machine room migration, and then took a look at the configuration file. The effort paid off. I really located the reason.
Looking at the scheduling configuration file, it turns out that the master's database configuration is modified normally (so the main functions are not affected), and the metadata configuration on the worker has not been completely modified
In the process of locating this problem, several big guys on the official website have been bothered by me. Thank you again for your patient guidance! !
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-dolphinscheduler] CalvinKirs commented on issue #4161: [Bug][SQL] SQL query mode exception : Failed to obtain JDBC Connection ...
Posted by GitBox <gi...@apache.org>.
CalvinKirs commented on issue #4161:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4161#issuecomment-738606424
Does the thread of the database itself reach the limit of max conn?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-dolphinscheduler] CalvinKirs commented on issue #4161: [Bug][SQL] SQL query mode exception : Failed to obtain JDBC Connection ...
Posted by GitBox <gi...@apache.org>.
CalvinKirs commented on issue #4161:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4161#issuecomment-739313862
> I have been tossing about the problem for a few days, and I have not been able to locate the specific cause. The driver has also been changed to 5.1.48, the server restarted and other methods have been tried without solution.
>
> It's hard to understand: other operations don't even have any problems with data. Only this sql component sql type is query, and the problem of druid timeout has been reported. I have been thinking about the details of eating, walking, and sleeping that I have overlooked. . . I finally decided on the machine room migration, and then took a look at the configuration file. The effort paid off. I really located the reason.
>
> Looking at the scheduling configuration file, it turns out that the master's database configuration is modified normally (so the main functions are not affected), and the metadata configuration on the worker has not been completely modified
>
> In the process of locating this problem, several big guys on the official website have been bothered by me. Thank you again for your patient guidance! !
Thx，I will close it.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org