github-actions[bot] commented on issue #9437:
URL: 
https://github.com/apache/dolphinscheduler/issues/9437#issuecomment-1094562031

   ### 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
   
   After successfully creating a hive data source from the ds page, execute the 
command in hive to delete the db corresponding to the ds. After about 20 
minutes, the apiserver starts to report the error that the connection to the db 
is not possible, and it keeps reporting errors, resulting in hive connection 
number is filled. This data source has not been used anywhere in ds since the 
page was created.
   
   ### What you expected to happen
   
   Only when using it report the error that the connection cannot be made
   
   ### How to reproduce
   
   1. Create a hive data source on the page, select a database that exists in 
hive, such as testdb, and add it successfully
   2. Beeline logs in to hive where the db created in step 1 is located, and 
executes the name drop database testdb;
   3. Observe the apiserver. log, and find that after about 20 minutes (or 
directly go to the page to edit the data source created in step 1, click Test 
Connection), an error that this database does not exist starts to report, and 
it keeps looping, which eventually leads to too many hive connections.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   2.0.5
   
   ### Are you willing to submit PR?
   
   - [X] 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