Skip to content

branch-4.1: [fix](connection) Prevent timeout checker from stopping after an exception #65040#65063

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-65040-branch-4.1
Open

branch-4.1: [fix](connection) Prevent timeout checker from stopping after an exception #65040#65063
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-65040-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #65040

…ption (#65040)

Problem Summary:

The connection timeout checker is scheduled with `scheduleAtFixedRate`.
If an unchecked exception escapes from the task,
`ScheduledThreadPoolExecutor` suppresses all subsequent executions. As a
result, expired connections may no longer be cleaned up.

This PR:

- Isolates exceptions from each `ConnectContext`, so one broken
connection does not prevent other connections from being checked.
- Adds an outer exception boundary to keep the periodic timeout checker
alive.
- Logs the stack trace together with the connection ID and user for
diagnosis.
- Adds a unit test verifying that timeout checking continues after one
context throws an exception.

This applies to both MySQL and Arrow Flight SQL connection pools.
@github-actions github-actions Bot requested a review from yiguolei as a code owner July 1, 2026 03:24
@hello-stephen

Copy link
Copy Markdown
Contributor

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

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 81.82% (9/11) 🎉
Increment coverage report
Complete coverage report

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 54.55% (6/11) 🎉
Increment coverage report
Complete coverage report

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.

2 participants