Chia-Ping Tsai created KAFKA-16611:
--------------------------------------
Summary: Consider adding test name to "client.id" of Admin in
testing
Key: KAFKA-16611
URL: https://issues.apache.org/jira/browse/KAFKA-16611
Project: Kafka
Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
I observed following errors many times.
{quote}
org.opentest4j.AssertionFailedError: Found 16 unexpected threads during
@BeforeAll: `kafka-admin-client-thread |
adminclient-287,kafka-admin-client-thread |
adminclient-276,kafka-admin-client-thread |
adminclient-271,kafka-admin-client-thread |
adminclient-293,kafka-admin-client-thread |
adminclient-281,kafka-admin-client-thread |
adminclient-302,kafka-admin-client-thread |
adminclient-334,kafka-admin-client-thread |
adminclient-323,kafka-admin-client-thread |
adminclient-257,kafka-admin-client-thread |
adminclient-336,kafka-admin-client-thread |
adminclient-308,kafka-admin-client-thread |
adminclient-263,kafka-admin-client-thread |
adminclient-273,kafka-admin-client-thread |
adminclient-278,kafka-admin-client-thread |
adminclient-283,kafka-admin-client-thread | adminclient-317` ==> expected:
<true> but was: <false>
{quote}
That could be caused by exceptional shutdown. Or we do have resource leaks in
some failed tests. Adding the test name to "client.id" can give hints about that
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
