-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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 ref count handling in Engine.failEngine #48639
Conversation
We can run into an already closed store here and hence throw on trying to increment the ref count => moving to the guarded ref count increment closes elastic#48625
Pinging @elastic/es-distributed (:Distributed/Recovery) |
@@ -490,7 +490,6 @@ public void testIndexAndRelocateConcurrently() throws Exception { | |||
docs[i] = client().prepareIndex("test").setId(id).setSource("field1", English.intToEnglish(numDocs + i)); | |||
} | |||
indexRandom(true, docs); | |||
numDocs *= 2; |
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 line is just dead code we're never touching numDocs
again in this 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.
LGTM
Thanks @dnhatn ! Sorry for pushing |
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.
LGTM. The new fix is better. Thanks @original-brownbear for an extra iteration :)
We can run into an already closed store here and hence throw on trying to increment the ref count => moving to the guarded ref count increment closes elastic#48625
I have backported this PR to 7.5 since #48414 needs it. |
We can run into an already closed store here and hence
throw on trying to increment the ref count => moving to
the guarded ref count increment
closes #48625