ruanwenjun commented on PR #13198: URL: https://github.com/apache/dolphinscheduler/pull/13198#issuecomment-1364618024
> > > > > @ruanwenjun To avoid using connections from thread pool? create a separated connection in each task? > > > > > > > > > > > > Yes, you can see the issue description. > > > > > > > > > Is it possible to create too many connections if there are lots of tasks? > > > > > > Yes, this will need to create connection for each processdure task, but right now, I don't find other solution. Since the temporary table is bound to the session, if we don't close the session the temporary will always exist. > > If we can't find another solution, then current is the best one. Too many connections for a DB is a disaster absolutely, dropping a temporary table is just a flaw. This is a bug, will cause the procedure task cannot use, the temporary table is shared by multiple task, if you create a template task in the procedure task, you will get an error, since there might already exist a temporary table with the same name created by another task. -- 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]
