Gabriel39 opened a new pull request, #68329: URL: https://github.com/apache/doris/pull/68329
### What problem does this PR solve? Related PR: #68101 `test_lower_case_meta_with_lower_table_conf_show_and_select` can exhaust the test user's connection quota while waiting for tables. Each independent Awaitility wait creates a polling thread whose JDBC connection is stored in `SuiteContext.threadLocalConn`; suite-thread cleanup cannot close those connections. In [build 1053466](http://43.132.222.7:8111/viewLog.html?buildId=1053466&buildTypeId=Doris_External_Regression), the polling thread repeatedly received `Reach limit of connections` before the case reported a 10-second metadata wait timeout. Use the existing `awaitUntil(10, 1)` helper, which polls on the suite thread and reuses its JDBC connection. Add a comment explaining the connection ownership requirement and remove the unused imports. This preserves the polling condition, interval and configured wait budget without increasing connection limits. ### Release note None ### Check List (For Author) - Test - [x] Manual test (details below) - [ ] Regression test on a running Doris cluster - Behavior changed: - [x] No production behavior change; test polling reuses the suite connection. - Does this need documentation? - [x] No. Validation: - Compiled the complete Groovy case with Groovy 3.0.8. - Evaluated the actual case wait closure and the framework's actual `awaitUntil` implementation with Awaitility 4.2.1, using thread-local stand-ins for JDBC connections. Three waits before the fix created three resources on three polling threads, none reachable by suite-thread cleanup; the same check after the fix created one resource on the suite thread and cleaned it up. The ownership assertion failed before the fix and passed after it. - `git diff --check` passed. - Full external regression remains to be validated in CI; the local ownership check does not establish end-to-end cluster stability. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
