Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[branch-2.1][improvement](jdbc catalog) Force all resources to be closed in the close method #39666

Merged
merged 1 commit into from
Aug 21, 2024

Conversation

zy-kkk
Copy link
Member

@zy-kkk zy-kkk commented Aug 21, 2024

pick (#39423)

Force all resources to be closed in the close method. In the previous logic, query errors or query cancellation will not force the connection to be closed, which will cause abnormal Hikari connection counts. Although forced connection closure will generate some error logs in some cases, we should have this bottom-line guarantee and refine the closing logic later.

…lose method (apache#39423)

Force all resources to be closed in the close method. In the previous
logic, query errors or query cancellation will not force the connection
to be closed, which will cause abnormal Hikari connection counts.
Although forced connection closure will generate some error logs in some
cases, we should have this bottom-line guarantee and refine the closing
logic later.
@zy-kkk
Copy link
Member Author

zy-kkk commented Aug 21, 2024

run buildall

@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR

Since 2024-03-18, the Document has been moved to doris-website.
See Doris Document.

@morningman morningman merged commit 80a27ca into apache:branch-2.1 Aug 21, 2024
21 of 22 checks passed
@zy-kkk zy-kkk deleted the fix_jdbc_close_21 branch August 21, 2024 11:37
@yiguolei yiguolei mentioned this pull request Sep 5, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants