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 2022/09/06 10:46:25 UTC

[GitHub] [dolphinscheduler] ruanwenjun commented on issue #11533: [Bug] [worker] Connections is not released after completing the SQL task

ruanwenjun commented on issue #11533:
URL: https://github.com/apache/dolphinscheduler/issues/11533#issuecomment-1237983253

   > > > > > > > Is this happen in 3.0.0-release or just beta?
   > > > > > > > There is a same issue #11120, but has already been fixed at 3.0.0-release.
   > > > > > > 
   > > > > > > 
   > > > > > > 3.0.0-release
   > > > > > 
   > > > > > 
   > > > > > 3.0.0release use DataSource in sql task, it will hold connection at default, you can reduce the [`minimumIdle`](https://github.com/brettwooldridge/HikariCP) to make the connection to be expire.
   > > > > 
   > > > > 
   > > > > I locally standalone changed minimumIdle to 1 for all modules, but the total link is still 5.
   > > > 
   > > > 
   > > > Could you please try to set the config `spring.datasource.minIdle=1` in `common.properties`.
   > > 
   > > 
   > > You are right, the connection decrease when I config common.properties. @ruanwenjun @chunhui5566 @mongooooo @simon824 But I think we should decrease default minIdle in code.
   > 
   > Thank you for you recheck and reply , i think the current problem is the connection not release, one day sooner or later it will still increased to more than 100 . Befor V3.0.0-beta1 the datasource be put in map and there is no such problem. now it in Guava Cache . Could it be the problem?
   
   Yes, in 3.0.0 release, we have fixed this bug.


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org