Uh oh!
There was an error while loading. Please reload this page.
PHOENIX-6329 Eliminate or serialize minicluster restart operations in… - #1101
PHOENIX-6329 Eliminate or serialize minicluster restart operations in…#1101stoty wants to merge 1 commit into
Conversation
stoty
commented
Jan 19, 2021
💔 -1 overall
This message was automatically generated. |
6b2e5ad to
a1b2ee4Comparestoty
commented
Jan 20, 2021
💔 -1 overall
This message was automatically generated. |
gjacoby126
left a comment
There was a problem hiding this comment.
+1, assuming that usage data shows this makes the tests more stable. Thanks @stoty
With this, we have perf advantage over #1080 but still full build took 4h16m. I believe a couple more build runs could provide clear results on both PRs. |
stoty
commented
Jan 22, 2021
Comparing the ASF jenkins runtimes is not trivial. We've got both 16 and 24 core machines in the pool, and there may or may not be another task running in parallel. |
stoty
commented
Jan 22, 2021
The last build had a successful test run (the maven shading bug caused a build failure, but that's a different issue) |
Got it, Thanks. I think it makes sense, anyways when I tried in my VM with and without #1080 , the difference was apparent. Anyways, synchronizing the key functionality of starting and shuting down miniCluster is necessary. Agree with moving forward with this patch after we have QA result for updated PR.
Great. |
stoty
commented
Jan 22, 2021
💔 -1 overall
This message was automatically generated. |
… Integration tests