gzqcason opened a new issue, #14795:
URL: https://github.com/apache/dolphinscheduler/issues/14795

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Sorry for mark the option 'No similar issues found' since I found the 
similar issues #13602 #13119 #13085  but not found any good solution to salve 
it.
   I'm using version 3.0.0
   When multiple sql-tasks with connecting hiveserver2 and scheduled at the 
same time, it seems that the Hive session will only be created once. which 
means that the first task can obtain the Hive connection, while other tasks 
will report the null pointer exception due to not obtaining the connection as 
follows.
   
   
![image](https://github.com/apache/dolphinscheduler/assets/79817470/631f67a4-7935-41ce-8293-f70e5b3adc22)
   
   
![image](https://github.com/apache/dolphinscheduler/assets/79817470/de3aef7a-41fe-47ed-a454-09ef79552885)
   
   
   
   ### What you expected to happen
   
   
![image](https://github.com/apache/dolphinscheduler/assets/79817470/8245d4b7-e5f6-4a52-b56c-cdf7e1d2c4f0)
   I execute the same sql-task several times, only the first one SUCCESS.
   Total number of hive sessions only increase once. I tried to change Hikari 
pool profile on work-server application.yaml but seams doesn't work.
   
   ### How to reproduce
   
   just manually executing the same sql-task several times and make sure each 
sql task runtime will be longer than 30s.
   
   ### Anything else
   
   It happens every time. Due to some reasons, i can't switch the version 
immediately. I would like to know if there is a fix for this issue in version 
3.2.x or later, which was achieved by canceling hive using the hikari pool?
   
   Looking forward to a reply. BR!
   
   ### Version
   
   dev
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to