-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Remote Store] Fix flaky test RemoteStoreIT.testRemoteSegmentStoreRestore #6252
[Remote Store] Fix flaky test RemoteStoreIT.testRemoteSegmentStoreRestore #6252
Conversation
public void testRemoteStoreRestoreFromRemoteSegmentStore() throws IOException { | ||
internalCluster().startNodes(3); | ||
public void testRemoteSegmentStoreRestore() throws IOException { | ||
internalCluster().startDataOnlyNodes(3); |
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 is not a fix to flakiness that was observed in #6248.
It is just to harden the test so that primary is not the cluster manager node as well.
*/ | ||
public void testStrictWeightedRouting() throws Exception { | ||
public void testStrictWeightedRouting() { |
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.
These un-documented @throws created issues while running the tests on local. Not related to the fix of the flaky test.
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.
@sachinpkale Which JDK are you using locally? I've seen inconsistencies with some non-LTS versions with regard to javadoc enforcement so I'd recommend using 11 or 17 if that is the cause here.
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.
@andrross the javadoc enforcement should not apply over test code, do you see checks enforced somewhere?
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.
@reta Just from this comment: #5995 (comment) I have no idea why JDK 14 seems to want to enforce javadoc rules against tests, but that's what Tianli's comment suggests is happening.
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.
Oh I see, thanks @andrross, I think we agreed to discard JDK-14 issues (and unsupported JDKs in general)
Gradle Check (Jenkins) Run Completed with:
|
Failing due to flaky test: #6255 Pushing empty commit to re-trigger the build. |
5975509
to
1e32c73
Compare
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
long maxSeqNo = 0; | ||
long maxSeqNoRefreshedOrFlushed = 0; | ||
long maxSeqNo = -1; | ||
long maxSeqNoRefreshedOrFlushed = -1; |
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 ^ is the fix for flakiness of the test.
Signed-off-by: Sachin Kale <kalsac@amazon.com>
1e32c73
to
0b5b1cb
Compare
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #6252 +/- ##
============================================
+ Coverage 70.72% 70.76% +0.04%
- Complexity 58791 58873 +82
============================================
Files 4782 4789 +7
Lines 281484 281794 +310
Branches 40642 40671 +29
============================================
+ Hits 199072 199412 +340
- Misses 65984 66021 +37
+ Partials 16428 16361 -67
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Signed-off-by: Sachin Kale <kalsac@amazon.com> (cherry picked from commit 4f5fd9c) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Signed-off-by: Sachin Kale kalsac@amazon.com
Description
RemoteStoreIT.testRemoteSegmentStoreRestore
test, if we index X documents and primary goes down without refresh, as we are using only remote segment store, restore operation creates as empty index.Issues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.