Use ContextManager as workaround to mitigate GC issues in some Admin tests #2131
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.





What
Some Admin module unit tests (e.g. test_list_consumer_group_offsets_api) finishes but after that the callback function (_make_consumer_group_offsets_result), running in the librdkafka's background, triggers garbage collection. When librdkafka detects that rd_kafka_destroy is invoked from its own thread (https://github.com/confluentinc/librdkafka/blob/616fb6e8074e82e0302f1c7d2896d7e577f8eb9b/src/rdkafka.c#L1115), it sends the ABORT signal
Using context manager as a workaround as it seems to help with cleaning up AdminClient object. To fix the root cause, we have to do a deeper investigation in librdkafka
Checklist
References
JIRA: https://confluentinc.atlassian.net/browse/NONJAVACLI-4105
Test & Review
Open questions / Follow-ups