-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDDS-2053. Fix TestOzoneManagerRatisServer failure. Contributed by Xi… #1373
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
Conversation
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
@xiaoyuyao, Xiaoyu, I cannot reproduce this test failure locally. Any extra step to reproduce it? |
|
Just try repeat the test run more than 1 times in IntelliJ, you will be able repro the metrics leak. |
|
I rerun the test dozens of times, sill cannot reproduce the issue. Don't know why. |
|
In the test Run/Debug Configuration, Choose "Repeat": "Until Failure" for the test case |
This comment has been minimized.
This comment has been minimized.
| .build(); | ||
| // Starts a single node Ratis server | ||
| omRatisServer.stop(); | ||
| OzoneManagerRatisServer newOmRatisServer = OzoneManagerRatisServer |
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.
@ChenSammi omRatisServer is started at the begin of each test case and stop after that. However in this new test case, it started a different OzoneManagerRatisServer named newOmRatisServer, it has to be stopped explicitly to avoid leak. Also, the omRatisServer has to be stopped before newOmRatisServer is started to avoid metric registration confliction.
adoroszlai
left a comment
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.
Thanks @xiaoyuyao for working on fixing this unit test.
|
Change LGTM. +1. |
…aoyu Yao.