-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[fix][test] Fix a resource leak in ClusterMigrationTest #21366
[fix][test] Fix a resource leak in ClusterMigrationTest #21366
Conversation
119752c
to
73d6dae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ClusterMigrationTest.testClusterMigrationWithReplicationBacklog
expected [false] but found [true]
Can you help take a look at this flaky test?
@Demogorgon314 I'm investigating. It seems to fail consistently after making the change of cleaning up resources properly. |
73d6dae
to
00ad7de
Compare
@Demogorgon314 PTAL, problem should be fixed now. |
@vineeth1995 @rdhabalia @vraulji567 I guess we should also consider moving ClusterMigrationTest to it's own test group since the test runtime duration is so long. WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
(cherry picked from commit 39235ed) # Conflicts: # pulsar-broker/src/test/java/org/apache/pulsar/broker/service/ClusterMigrationTest.java
(cherry picked from commit 39235ed)
(cherry picked from commit 39235ed) # Conflicts: # pulsar-broker/src/test/java/org/apache/pulsar/broker/service/ClusterMigrationTest.java
(cherry picked from commit 39235ed) # Conflicts: # pulsar-broker/src/test/java/org/apache/pulsar/broker/service/ClusterMigrationTest.java
Motivation
Running ClusterMigrationTest could fail with OOME.
When investigating the problem, it showed up that ClusterMigrationTest's TestBroker inner class doesn't clean up resources properly. The admin clients weren't closed.
Modifications
super.internalCleanup()
in thecleanup
method.Documentation
doc
doc-required
doc-not-needed
doc-complete