-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Simplify Snapshot ITs Further #63655
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
Simplify Snapshot ITs Further #63655
Conversation
Removing some more duplication and redundant logic.
|
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
| protected void awaitMasterFinishRepoOperations() throws Exception { | ||
| logger.info("--> waiting for master to finish all repo operations on its SNAPSHOT pool"); | ||
| final ThreadPool masterThreadPool = internalCluster().getMasterNodeInstance(ThreadPool.class); | ||
| final ThreadPool masterThreadPool = internalCluster().getCurrentMasterNodeInstance(ThreadPool.class); |
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.
This actually fixes a bug, we just didn't see the bug in practice yet because we only used this method in tests with a single master node ...
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.
Yeah, I noticed similar issue in DiskThresholdDeciderIT. getMasterNodeInstance() is trappy and should be renamed.
|
Thanks Tanguy! |
* Removing some more duplication and redundant logic. * Aligning all timeouts to 30s (60s or even 10 minute timeouts should be unnecessary, if they aren't we should figure out why) * Remove some usage of `actionGet()` in tests (it's just evil to suppress the stack-trace)
actionGet()in tests (it's just evil to suppress the stack-trace)